[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #57771] [Manual] Compiling Octave with 64-bit
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #57771] [Manual] Compiling Octave with 64-bit indexing |
Date: |
Sat, 8 Feb 2020 16:01:28 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.87 Safari/537.36 |
Follow-up Comment #2, bug #57771 (project octave):
LAPACK - Yeah, looks like the 'NOOPT' variable has been renamed to
'FFLAGS_NOOPT' recently. The docs should probably refer to either variable
name, for example "the variable NOOPT or FFLAGS_NOOPT, depending on your
version of LAPACK". You don't have to build LAPACK with CMake, I don't, so
better to avoid mentioning CMake specific variables (users who prefer CMake
probably know what they are doing).
QRUPDATE - When I build QRUPDATE for 64-bit integers, I just pass LDFLAGS as
an argument to 'make' to point to wherever the custom BLAS and LAPACK
libraries are.
SuiteSparse - Last time I built SuiteSparse version 4.5.5, I only need to pass
'BLAS=-lblas' as an argument to the 'make' command to get it to build the way
I want. Does that work for you?
ARPACK - Sure, I ran configure with "--with-blas=blas" and
"--with-lapack=lapack", and used LDFLAGS again to specify the library
directory, but equivalent. I don't build with "--enable-mpi".
If you want to compare and refine your build rules, both Kai and myself have
projects to build Octave and all dependencies with 64-bit Fortran integers.
* https://gitlab.com/mtmiller/octave-blas64-builder
* https://github.com/octave-de/GNU-Octave-enable-64
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57771>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/