Hi, I'm having problems creating a shared library using automake/libtool. Some of the object code in the library is mpi code, so the library needs to be linked with mpicc, which is shell script that runs gcc with the appropriate options to link against the MPICH libraries. With libtool versions <= 1.3.3 I can set CC=mpicc in the Makefile.am that builds the lib and it runs as expected: ------ /bin/sh ../libtool --mode=link mpicc -g -O2 -Wall -o liblal.la -rpath /usr/local/lib LALEmpty.lo ../packages/burstsearch/src/ExcessPower.lo ( a bunch of other object files ) ../packages/window/src/Window.lo -lFrame -lsrfftw -lsfftw -lm rm -fr .libs/liblal.la .libs/liblal.* .libs/liblal.* mpicc -shared LALEmpty.lo ../packages/burstsearch/src/ExcessPower.lo ../packages/burstsearch/src/TFTransform.lo ( a bunch of other object files ) ../packages/window/src/Window.lo -lFrame -lsrfftw -lsfftw -lm -lc -Wl,-soname -Wl,liblal.so.0 -o .libs/liblal.so.0.0.o ------ However with libtool >= 1.3.4 it ignores mpicc and links with gcc, so liblal.so isn't linked against the mpi libraries. ------ /bin/sh ../libtool --mode=link mpicc -g -O2 -Wall -o liblal.la -rpath /usr/local/lib LALEmpty.lo ../packages/burstsearch/src/ExcessPower.lo ( a bunch of other object files ) ../packages/window/src/Window.lo -lFrame -lsrfftw -lsfftw -lm rm -fr .libs/liblal.la .libs/liblal.* .libs/liblal.* gcc -shared LALEmpty.lo ../packages/burstsearch/src/ExcessPower.lo ( a bunch of other object files ) ../packages/window/src/Window.lo -lFrame -lsrfftw -lsfftw -lm -lc -Wl,-soname -Wl,liblal.so.0 -o .libs/liblal.so.0.0.0 ------ Any idea as to what is going on here and what has changed between 1.3.3 and 1.3.4? I have tried setting LD=mpicc in the configure.in before libtool is made, but it ltconfig seems to think that mpicc can't build shared libs, so that doesn't work. Thanks, Duncan. -- Duncan Brown University of Wisconsin-Milwaukee [EMAIL PROTECTED] Physics Department, 1900 E. Kenwood http://www.lsc-group.phys.uwm.edu/~duncan Milwaukee, WI 53211, USA
