Hi Josh, * Josh Hursey wrote on Mon, Mar 20, 2006 at 06:48:55PM CET: > On Mar 20, 2006, at 12:13 PM, Ralf Wildenhues wrote: > >* Josh Hursey wrote on Mon, Mar 20, 2006 at 06:05:29PM CET: > >>I recently ran into a build problem using the Portland 5.2 compilers > >>on Odin (x86_64). It looks like the soft link is broken in the build > >>system. > >>It is linked to libopal.so.0.0.0 instead of libopal.so.0 > > > >Do you still have the complete build log? The place where libopal is > >created is interesting, as well as './libtool --config'. > > Sorry I forgot to include that. Should be attached now.
Hmm. Could you go into $top_builddir/opal and do ../libtool --mode=clean rm -f libopal.la make 2>&1 | tee makelog and send makelog? After that, the .libs subdirectory should look more or less like this (the *.la* may vary a bit): libopal.la -> ../libopal.la libopal.lai libopal.so -> libopal.so.0.0.0 libopal.so.0 -> libopal.so.0.0.0 libopal.so.0.0.0 Otherwise, I cannot detect much that looks suspicious. This is weird, but it looks unrelated: | configure:130244: checking whether a statically linked program can dlopen itself | configure:130318: pgcc -o conftest -O -DNDEBUG -D_REENTRANT -DHAVE_DLFCN_H -Wl,--export-dynamic -Bstatic conftest.c -ldl -lm -lutil -lnsl -lpthread >&5 | /tmp/pgccbaaaapoxac.o(.text+0x28): In function `main': | : warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking | configure:130321: $? = 0 | /u/jjhursey/local/odin/ompi/devel/lib/: cannot read file data: Is a directory | configure:130339: result: no Thanks, Ralf
