[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #44370] Octave compiler flags used at build ti

From: Carnë Draug
Subject: [Octave-bug-tracker] [bug #44370] Octave compiler flags used at build time are not used by mkoctfile
Date: Wed, 25 Feb 2015 17:23:39 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Iceweasel/31.4.0


                 Summary: Octave compiler flags used at build time are not
used by mkoctfile
                 Project: GNU Octave
            Submitted by: carandraug
            Submitted on: Wed 25 Feb 2015 17:23:38 GMT
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux



I may be wrong on this premise but I was under the impression that part of the
job of mkoctfile was setting up all the flags required to build oct files.
Part of this job would be replicating the compiler flags used to build

However, this does not seem to be the case. Because of the place where hdf5
libraries are installed in Debian systems (see bug #38928), one needs to set
--with-hdf5-includedir=... and --with-hdf5-libdir=... during configure.  These
are not passed on to mkoctfile. I checked all the flags available to print
from mkoctfile and I could not find them anywhere.

The end result is that package installation fails because hdf5 headers are not
in the CPP path even though the package has nothing to do with hdf5 (side
effect of bug #43180)


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]