octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #32009] Issues with OCT-files and LAPACK


From: Lukas Reichlin
Subject: [Octave-bug-tracker] [bug #32009] Issues with OCT-files and LAPACK
Date: Mon, 24 Jan 2011 12:15:32 +0000
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-us) AppleWebKit/533.19.4 (KHTML, like Gecko) Version/5.0.3 Safari/533.19.4

Follow-up Comment #4, bug #32009 (project octave):

"every mkoctfile command" means mkoctfile commands in the makefile_* [1] (all
except makefile_helpers and makefile_all). In revision 8055, I removed the
flags and added them again in revision 8063. See [2] for an example. This
example is the failing test from comment #2. TG01JD.f is the SLICOT routine
which won't pass the test provided by its authors.

Today, Jarno Rajahalme posted on the maintainer list:

++
I have been building Octave from sources on OSX using GCC 4.5. To avoid
crashes LDFLAGS needs to have the newer libstdc++ as the first file to be
linked with, like:

export LDFLAGS="/opt/local/lib/gcc45/libstdc++.6.dylib"

(Above before ./configure)

Without this Octave segfaults when compiled with newer-than-Apple GCC.

Also, Apple blas (vecLib) does not work with 64-bit gfortran (4.2, 4.3, 4.4,
nor 4.5). Complex functions obviously fail (and segment fault) without -ff2c
option, but then other non-complex routines return incorrect answers when
-ff2c is enabled, so that configure fails. So with 64-bit OSX you pretty much
have to use atlas and/or lapack.

Would information like this be of interest in README.MacOS?

Jarno
--

Ben and I exchanged a few mails about README.MacOS and I have tried to
configure octave-devel with
++
--with-blas="-Wl,-framework -Wl,vecLib"
--

in a first attempt and added stuff like
++
configure.fflags-delete    -pipe -m64
configure.fflags-append    -ff2c -g -m32
--

and had exactly the config failures that Jarno describes.

My  octave_config_info.config_opts  for successful 3.3.90 builds are
++
'--prefix=/opt/local'
'--without-x'
'--enable-shared'
'--enable-dl'
'--disable-docs'
'--disable-openmp'
'--enable-readline'
'--enable-extra-warning-flags'
'--with-qhull'
'--with-z'
'--with-hdf5'
'--with-fftw3'
'--with-fftw3f'
'--with-glpk'
'--with-curl'
'--with-blas'
'--with-lapack'
'--with-qrupdate'
'--with-amd'
'--with-camd'
'--with-colamd'
'--with-ccolamd'
'--with-cholmod=-lcholmod -lmetis'
'--with-cxsparse'
'--with-umfpack'
'--with-arpack'
'CC=/opt/local/bin/gcc-mp-4.4'
'CFLAGS=-pipe -O2 -m64'
'LDFLAGS=-L/opt/local/lib'
'CPPFLAGS=-I/opt/local/include'
'CXX=/opt/local/bin/g++-mp-4.4'
'CXXFLAGS=-pipe -O2 -m64'
'F77=/opt/local/bin/gfortran-mp-4.4'
'FFLAGS=-pipe -O2 -m64'
--

but with these builds I need to add the mac-specific flags to mkoctfile calls
like [2] which is exactly what I want to avoid.

Best Regards,
Lukas


[1]
http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/control/devel/

[2]
http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/control/devel/makefile_minreal.m?r1=8055&r2=8063


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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