[SciPy-user] tracebacks when running tests

Fernando Perez fperez at colorado.edu
Thu Jun 3 10:15:40 CDT 2004

Elliot Peele wrote:

> Looking at the ldd output for clapack.so:
> [elliot at rkbuild linalg]$ ldd clapack.so
>         liblapack.so.3 => /usr/lib/liblapack.so.3 (0xb6eb4000)
>         libg2c.so.0 => /usr/lib/libg2c.so.0 (0xb6e96000)
>         libm.so.6 => /lib/tls/libm.so.6 (0xb6e74000)
>         libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb6e6a000)
>         libc.so.6 => /lib/tls/libc.so.6 (0xb6d32000)
>         libblas.so.3 => /usr/lib/libblas.so.3 (0xb6ce2000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
> It links against liblapack.so.3 which doesn't include the symbols that
> were added from atlas since they are in liblapack.a. Is there anyway to
> fix this?

Pearu already gave you the solution, so here I'm just providing you the link 
to my very same question from yesterday, but on scipy-dev.  This is the thread 
where Pearu mentioned my almost finding that /usr/lib/atlas is the best 
location for the atlas-enabled static libs to live, so that conflicts with the 
dynamic ones are avoided:




More information about the SciPy-user mailing list