[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #50339] configure detection for BLAS does not
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #50339] configure detection for BLAS does not use -fdefault-integer-8 |
Date: |
Fri, 8 Sep 2017 22:08:43 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Follow-up Comment #11, bug #50339 (project octave):
That's what I thought.
I am now able to build Octave with all of the Fortran libraries built for
64-bit integers and all tests pass. But I have to build with the following:
./configure \
CPPFLAGS='-DLONGBLAS=long -DBLAS64' \
F77_INTEGER_8_FLAG=-fdefault-integer-8 \
...
The -D options might not be necessary, they are only for the SuiteSparse
include files. I'll see if I can simplify that part.
But the F77_INTEGER_8_FLAG is necessary to pass into Octave's configure so
that it applies it when testing the various libraries. Otherwise configure
just errors out like I showed in comment #9.
Alternatively I think I can set FFLAGS="-g -O2 -fdefault-integer-8" and
configure will just think that the Fortran compiler does everything right by
default.
This is still an improvement over the previous --enable-64 behavior, we now
have a consistent octave_idx_type on 64-bit systems regardless of how the
Fortran libraries were built. I don't know that I'd call this a regression.
Before the user had to pass --enable-64, now they have to pass something else,
everything works both ways assuming the right libraries and the right flags
are given.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50339>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/