[SciPy-user] numpy/scipy+ATLAS on SuSE10.0/gcc4 (once more)

Christian Kristukat ckkart at hoc.net
Tue Mar 7 00:22:11 CST 2006


Hi,
I've got some observations to share concerning the compilation of numpy/scipy
with ATLAS on SuSE10.0
In some earlier posts I told everybody to use gfortran to build
numpy/scipy/ATLAS. Although the compilation worked without errors and
numpy/scipy seemed to work as well, Robert prooved, that gfortran is causing
serious faults so that scipy eventually fails during execution.
Originally I have chosen to use gfortran because every attempt to build
numpy/scipy/ATLAS on SuSE10.0 using gcc4 and g77 failed. I will shortly describe
what I tried (with gcc4/g77)

1) using SUSE10.0 blas and lapack rpms

Python 2.4.1 (#1, Sep 13 2005, 00:39:20)
[GCC 4.0.2 20050901 (prerelease) (SUSE Linux)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
import linalg -> failed: /usr/lib/libblas.so.3: undefined symbol: _gfortran_filename
>>>

2) with ATLAS

Python 2.4.1 (#1, Sep 13 2005, 00:39:20)
[GCC 4.0.2 20050901 (prerelease) (SUSE Linux)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
import linalg -> failed:
/usr/lib/python2.4/site-packages/numpy/linalg/lapack_lite.so: undefined symbol:
_gfortran_copy_string
>>>

3) using self compiled lapack and blas works!!

Can anyone figure out what the problem is and propose what to try next?

Regards, Christian



More information about the SciPy-user mailing list