[SciPy-dev] Stupid question.

[Fernando Pérez]

> This should not be gcc specific. Anyway, try
> 
> gcc -shared build/temp.linux-i686-2.2/fftw_wrap.o \
> -L/usr/local/home/fperez/lib -Lbuild/temp.linux-i686-2.2 \
> /usr/local/lib/libfftw_threads.so.2 \
> /usr/local/lib/librfftw_threads.so.2 \
> /usr/local/lib/libfftw.so.2 \
> /usr/local/lib/librfftw.so.2 \
> -lpthread \
> -o  build/lib.linux-i686-2.2/scipy/fftw/fftw.so

Yes Pearu,  it works.

To summarize: I removed my hand-made symlinks to restore the system to the
condition it's in when you install the rpms linked to at scipy.org. Then,
running python setup build fails at:

[scipy2]> gcc -shared build/temp.linux-i686-2.2/fftw_wrap.o
-L/usr/local/home/fperez/lib -Lbuild/temp.linux-i686-2.2 -lfftw_threads
-lrfftw_threads -lfftw -lrfftw -lpthread -lc_misc -lcephes -lgist -o
build/lib.linux-i686-2.2/scipy/fftw/fftw.so
/usr//bin/ld: cannot find -lfftw_threads
collect2: ld returned 1 exit status

Now, changing the above command by hand to:

[scipy2]> gcc -shared build/temp.linux-i686-2.2/fftw_wrap.o
-L/usr/local/home/fperez/lib -Lbuild/temp.linux-i686-2.2
/usr/local/lib/libfftw_threads.so.2 /usr/local/lib/librfftw_threads.so.2
/usr/local/lib/libfftw.so.2 /usr/local/lib/librfftw.so.2 -lpthread -o
build/lib.linux-i686-2.2/scipy/fftw/fftw.so


works fine. So I guess it's either for the users to hand-fix the links, or for
setup.py to work around the issue by incorporating Pearu's idea. Even if
kludgy, that sounds much better.

Cheers,

f.