[Numpy-discussion] OpenSuse 10.2 and numpy

Charles R Harris charlesr.harris at gmail.com
Wed Jan 3 23:37:39 CST 2007


On 1/3/07, Nils Wagner <nwagner at iam.uni-stuttgart.de> wrote:
>
> Hi all,
>
> I have tried to build the latest numpy on a 64-bit machine
> using OpenSuSE10.2.
> I have build BLAS, LAPACK and ATLAS from scratch (g77).
>
> python setup.py build yields
>
> ...
> creating build/temp.linux-x86_64-2.5/numpy/linalg
> compile options: '-DATLAS_INFO="\"3.7.11\""
> -Inumpy/core/include
> -Ibuild/src.linux-x86_64-2.5/numpy/core -Inumpy/core/src
> -Inumpy/core/include -I/usr/include/python2.5 -c'
> gcc: numpy/linalg/lapack_litemodule.c
> /usr/bin/g77 -g -Wall -shared
> build/temp.linux-x86_64-2.5/numpy/linalg/lapack_litemodule.o
> -L/usr/local/lib/atlas -L/usr/lib/python2.5/config
> -llapack -lf77blas -lcblas -latlas -lpython2.5 -lg2c -o
> build/lib.linux-x86_64-2.5/numpy/linalg/lapack_lite.so
>
> /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.5/../../../../x86_64-suse-linux/bin/ld:
> cannot find -lgcc_s
>
> /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.5/../../../../x86_64-suse-linux/bin/ld:
> cannot find -lgcc_s
> error: Command "/usr/bin/g77 -g -Wall -shared
> build/temp.linux-x86_64-2.5/numpy/linalg/lapack_litemodule.o
> -L/usr/local/lib/atlas -L/usr/lib/python2.5/config
> -llapack -lf77blas -lcblas -latlas -lpython2.5 -lg2c -o
> build/lib.linux-x86_64-2.5/numpy/linalg/lapack_lite.so"
> failed with exit status 1
>
> Any pointer how to fix this problem is appreciated.
>
> Nils
>
> g77 -v
> Reading specs from
> /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.5/specs
> Configured with: ../configure --enable-threads=posix
> --prefix=/usr --with-local-prefix=/usr/local
> --infodir=/usr/share/info --mandir=/usr/share/man
> --enable-languages=c,f77 --disable-checking
> --libdir=/usr/lib64 --disable-libgcj --with-slibdir=/lib64
> --with-system-zlib --enable-shared --enable-__cxa_atexit
> x86_64-suse-linux
> Thread model: posix
> gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
> nwagner at noname:~/svn/numpy> gcc -v
> Using built-in specs.
> Target: x86_64-suse-linux
> Configured with: ../configure --enable-threads=posix
> --prefix=/usr --with-local-prefix=/usr/local
> --infodir=/usr/share/info --mandir=/usr/share/man
> --libdir=/usr/lib64 --libexecdir=/usr/lib64
> --enable-languages=c,c++,objc,fortran,obj-c++,java,ada
> --enable-checking=release
> --with-gxx-include-dir=/usr/include/c++/4.1.2 --enable-ssp
> --disable-libssp --disable-libgcj --with-slibdir=/lib64
> --with-system-zlib --enable-shared --enable-__cxa_atexit
> --enable-libstdcxx-allocator=new --program-suffix=-4.1
> --enable-version-specific-runtime-libs
> --without-system-libunwind --with-cpu=generic
> --host=x86_64-suse-linux
> Thread model: posix
> gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)


You might check the location of python. ISTR that SUSE puts it in
/usr/local/lib, or maybe it is in one of the lib64 directories if you are
running 64 bit linux. In any case, the directories -L/usr/local/lib/atlas
-L/usr/lib/python2.5/config look suspicious to me. Apart from that I don't
have any suggestions.

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://projects.scipy.org/pipermail/numpy-discussion/attachments/20070103/d1d22719/attachment.html 


More information about the Numpy-discussion mailing list