On Friday 09 February 2007 09:00, Jaap Spies wrote: > William Stein wrote: > > Anyways, let me know what ldd tells you. > > > > > > > > -- William
> ldd > /home/jaap/downloads/sage-2.1/local/lib/python2.5/site-packages/sage/matrix >/matrix_modn_dense.so linux-gate.so.1 => (0x00ebf000) > libntl.so => not found > libgmp.so.3 => /usr/lib/sse2/libgmp.so.3 (0x00968000) > libgmpxx.so.3 => /usr/lib/sse2/libgmpxx.so.3 (0x00fd1000) > libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00203000) > libgivaro.so.0 => not found > libgslcblas.so.0 => /usr/lib/libgslcblas.so.0 (0x005c0000) > libcsage.so.0 => not found > libm.so.6 => /lib/libm.so.6 (0x00d63000) > libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00cd9000) > libpthread.so.0 => /lib/libpthread.so.0 (0x002ed000) > libc.so.6 => /lib/libc.so.6 (0x00a2c000) > /lib/ld-linux.so.2 (0x009ef000) > > Jaap Hi, it seems like if you have a system wide GSL installation. I would be interested in which GSL gets picked up by LinBox. To check this ldd needs to be run "in the context of SAGE". $ export SAGE_ROOT=/home/jaap/downloads/sage-2.1/ $ source $SAGE_ROOT/local/bin/sage-env $ ldd <path to matrix_modn> I just linked LinBox against the GSL as shipped with SAGE and that worked on my x86-64 Debian Etch. Maybe the build process picks up the wrong GSL? So, would you provide two objdumps for me? objdump -t of the system wide GSLCBlas and one objdump -t of the GSLCBlas as included with SAGE? Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _www: http://www.informatik.uni-bremen.de/~malb _jab: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
