problem with FFT module from Numeric 20.2.0

P. Alejandro Lopez-Valencia dradul at yahoo.com
Tue Oct 9 16:46:24 CEST 2001


In article <GKvyxB.9x3 at leeds.ac.uk>, nde at comp.leeds.ac.uk says...
>On Sat, 6 Oct 2001 09:37:36 -0500,
>P. Alejandro Lopez-Valencia <dradul at yahoo.com> wrote:
>> The solution is to be explicit. Edit your file 
>> /usr/local/lib/python21/config/Makefile in the appropriate places (3,  I 
>> don't recall their names off-had) to pass -R linker flags to ld. For 
>> example, I have added this in our lab box:
>> 
>>  -R/usr/lib -R/usr/local/lib -R/usr/local/ssl/lib -R/usr/openwin/lib
>> 
>> Without these linker flags modules like socket and pyexpat won't work at 
>> all if called from restricted execution environments where you don't 
>> want a full environemnt definition, namely CGI's and batch jobs.
>> 
>
>I'm working on Linux; do problems of this nature affect Linux
>also, or are they a Solaris-only thing?

As Malcom Treddinnick points out the problem is the half hearted job of 
the Solaris linker. In Linux, at least on Debian and Redhat, you can 
always edit /etc/ldconfig and get over with it :)

>But if this is the cause of the problem, why are the other modules
>from the Numeric package unaffected?  Why just fftpack?

That's strange, and should not happen. See:

bash-2.05$ ldd fftpack.so 
        libgcc_s.so.1 =>         /usr/local/lib/libgcc_s.so.1
        libc.so.1 =>     /lib/libc.so.1
        libdl.so.1 =>    /lib/libdl.so.1

and 

bash-2.05$ ldd _numpy.so 
        libgcc_s.so.1 =>         /usr/local/lib/libgcc_s.so.1
        libc.so.1 =>     /lib/libc.so.1
        libdl.so.1 =>    /lib/libdl.so.1

bash-2.05$ ldd /usr/local/bin/python
        libstdc++.so.3 =>        /usr/local/lib/libstdc++.so.3
        libpthread.so.1 =>       /lib/libpthread.so.1
        libsocket.so.1 =>        /lib/libsocket.so.1
        libnsl.so.1 =>   /lib/libnsl.so.1
        libdl.so.1 =>    /lib/libdl.so.1
        libthread.so.1 =>        /lib/libthread.so.1
        libm.so.1 =>     /lib/libm.so.1
        libc.so.1 =>     /lib/libc.so.1
        libgcc_s.so.1 =>         /usr/local/lib/libgcc_s.so.1
        libmp.so.2 =>    /lib/libmp.so.2

bash-2.05$ ldd  /usr/local/lib/libgcc_s.so.1
warning: ldd: /usr/local/lib/libgcc_s.so.1: is not executable
        libc.so.1 =>     /lib/libc.so.1
        libdl.so.1 =>    /lib/libdl.so.1


>Confused,

Hey! I've been using Solaris for at least 10 years and it still bites me 
back every day ;)

-- 
P. Alejandro Lopez-Valencia

Kenkon Itteki       ---       Heaven and Earth at one stroke




More information about the Python-list mailing list