[SciPy-dev] Link problem with scipy on SUN ?

Arnd Baecker a.backer at bristol.ac.uk
Sun Oct 21 16:49:42 EDT 2001


Hi,

when trying to install scipy I ran into the following
link problem under SUN
(uname -a: SunOS wega 5.8 Generic_108528-07 sun4u sparc
- I can provide further details if necessary)


[...]
cluster/src/vq_wrap.cpp: In function `int char_to_numtype(char)':
cluster/src/vq_wrap.cpp:590: warning: control reaches end of non-void
function `char_to_numtype(char)'
cluster/src/vq_wrap.cpp: At top level:
cluster/src/vq_wrap.cpp:516: warning: `struct PyObject *
l_output_helper(struct PyObject *, struct PyObject *)' defined but not
used
gcc -shared build/temp.solaris-2.8-sun4u-2.1/vq_wrap.o -L(null) -LSun/lib
-L(null) -LSun/lib -Lbuild/temp.solaris-2.8-sun4u-2.1
-Lbuild/temp.solaris-2.8-sun4u-2.1 -R(null) -RSun/lib -lamos -ltoms
-lfitpack -lminpack -lquadpack -lodepack -llinpack_lite -lmach -lf90 -lF77
-lM77 -lsunmath -lm -lgist -lc_misc -lcephes -o
build/lib.solaris-2.8-sun4u-2.1/scipy/cluster/_vq.so -mimpure-text
ld: fatal: library -lf90: not found
ld: fatal: library -lF77: not found
ld: fatal: library -lM77: not found
ld: fatal: library -lsunmath: not found
ld: fatal: File processing errors. No output written to
build/lib.solaris-2.8-sun4u-2.1/scipy/cluster/_vq.so
collect2: ld returned 1 exit status
error: command 'gcc' failed with exit status 1


If I replace the above line by 

gcc -shared build/temp.solaris-2.8-sun4u-2.1/vq_wrap.o -L(null) -LSun/lib
-L(null) -LSun/lib -Lbuild/temp.solaris-2.8-sun4u-2.1
-Lbuild/temp.solaris-2.8-sun4u-2.1 -R(null) -RSun/lib -lamos -ltoms
-lfitpack -lminpack -lquadpack -lodepack -llinpack_lite -lmach -L -lf90 -L
-lF77 -L -lM77 -L -lsunmath -lm -lgist -lc_misc -lcephes -o
build/lib.solaris-2.8-sun4u-2.1/scipy/cluster/_vq.so -mimpure-text 

then there is no problem anymore.
(i.e. adding -L in front of the above libraries does the job ...)

What do I have to change to get rid of this problem ?
(All the above four libraries seem to be defined in 
the variable self.libraries in build_flib.py.
but I don't understand enough python yet ... ;-)

Best,

Arnd




More information about the SciPy-Dev mailing list