[Octave-bug-tracker] [bug #30214] inconsistent FFLAGS treatment in --enable-64

[Jaroslav Hajek]

URL:
  <http://savannah.gnu.org/bugs/?30214>

                 Summary: inconsistent FFLAGS treatment in --enable-64
                 Project: GNU Octave
            Submitted by: highegg
            Submitted on: Tue 22 Jun 2010 12:15:06 PM GMT
                Category: Configuration and Build System
                Severity: 3 - Normal
              Item Group: Other
                  Status: None
             Assigned to: highegg
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Just moving the bug here from the mailing list.

Although configure --enable-64 correctly
discovers that Fortran doesn't have -fdefault-integer-8, it doesn't
add it to FFLAGS, but only stores it into a variable called
F77_INTEGER_8_FLAG. Is there any reason for this? I think it used to
be added to FFLAGS in past (probably prior to libtool changes).
Because of this, ACX_BLAS_F77_FUNC fails to detect an incompatible
BLAS library (it uses just FFLAGS). Worse yet, mkoctfile compiles
Fortran files with wrong flags (i.e. again without the
-fdefault-integer-8). libcruft, on the contrary, uses
F77_INTEGER_8_FLAG explicitly in libcruft/Makefile.am.

We should fix configure to temporarily add F77_INTEGER_8_FLAG to FFLAGS prior
to BLAS checking, and we should also fix mkoctfile to include
F77_INTEGER_8_FLAG in ALL_FLAGS.





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?30214>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/