Well, as a quick hack, you can try adding --disable-dlopen to the configure line. It will disable the building of individual components (instead linking them into the main shared libraries). It means that you have to be slightly more careful about which components you build, but in practice usually makes things a little bit easier, especially when cross compiling (less things to move around).

Brian

On Thu, 10 Apr 2008, Bailey, Eric wrote:

Hi,

I found an archive email with the same basic error I am running into for
mpi 1.2.6, unfortunately other then the question and request for the
output, there was not an email response on how it was solved.

the error

../../../opal/.libs/libopen-pal.so: undefined reference to
`lt_libltdlc_LTX_preloaded_symbols'

Here is the email link for the 1.2.4 problem..

http://www.open-mpi.org/community/lists/users/2007/10/4310.php

The email is a response by Jeff Squyres to the originator Jorge Parra.
Can either of you help?

here is my make output failure.. basically identical to the one reported
for mpi 1.2.4

make[2]: Entering directory
`/tmp/MPI/openmpi-1.2.6-7448/opal/tools/wrappers'
/bin/sh ../../../libtool --tag=CC   --mode=link ppc74xx-linux-gcc  -O3
-DNDEBUG -finline-functions -fno-strict-aliasing -pthread
-export-dynamic   -o opal_wrapper opal_wrapper.o
../../../opal/libopen-pal.la -lnsl -lutil  -lm
libtool: link: ppc74xx-linux-gcc -O3 -DNDEBUG -finline-functions
-fno-strict-aliasing -pthread -o .libs/opal_wrapper opal_wrapper.o
-Wl,--export-dynamic  ../../../opal/.libs/libopen-pal.so -ldl -lnsl
-lutil -lm -pthread -Wl,-rpath
-Wl,/home/MPI/openmpi-1.2.6-install-7448/lib
../../../opal/.libs/libopen-pal.so: undefined reference to
`lt_libltdlc_LTX_preloaded_symbols'
collect2: ld returned 1 exit status
make[2]: *** [opal_wrapper] Error 1
make[2]: Leaving directory
`/tmp/MPI/openmpi-1.2.6-7448/opal/tools/wrappers'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/MPI/openmpi-1.2.6-7448/opal'
make: *** [all-recursive] Error 1

Any help is greatly appreciated.

thanks,
Eric Bailey

Reply via email to