[Top][All Lists]

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

[Octave-bug-tracker] [bug #44359] FFLAGS not set correctly now

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #44359] FFLAGS not set correctly now
Date: Tue, 24 Feb 2015 03:09:51 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.111 Safari/537.36


                 Summary: FFLAGS not set correctly now
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Mon 23 Feb 2015 10:09:49 PM EST
                Category: Configuration and Build System
                Severity: 4 - Important
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any



The changes to save and restore the user compiler flags aren't working quite
right with FFLAGS.

One problem is that FFLAGS is saved way too early, before the defaults are set
and the compiler detected. If FFLAGS is not given to configure by the user, it
will always be empty.

Another problem is that there is no XTRA_FFLAGS. A few flags may have been
added to FFLAGS in previous versions of Octave, such as -mieee or -ff2c. I
think these will now be discarded at the end of configure. It might not be too
hard to introduce an XTRA_FFLAGS variable to handle these for the liboctave

I'll take a look at this if jwe or rik don't beat me too it.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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