Hello Richard, * Richard Graham wrote on Thu, Jan 10, 2008 at 10:14:46PM CET: > I am trying to build Open MPI on the Cray's (Compute Node Linux), and ran > into the following problem. In our configure script we get the wl parameter > set to -Wl, > > But when the following part of the build is run: > > /bin/sh ../../../libtool --tag=CC --mode=link cc -O2 > -I/opt/xt-pe/default/include/ -L/opt/xt-mpt/default/lib/snos64/ -o > orteboot orteboot.o ../../../orte/libopen-rte.la -lnsl -lutil -lpct > -lalpslli -lalpsutil > > It results in: > cc -O2 -I/opt/xt-pe/default/include/ -o orteboot orteboot.o [...] > -lalpslli -lalpsutil --rpath /opt/torque/2.2.0-snap.200711011704/lib --rpath > /opt/torque/2.2.0-snap.200711011704/lib > > Loosing the -Wl, value. Insteat of -Wl,--rpath I get --rpath, which the pgi > compiler does not recognize. Are there any hints on how to trouble shoot > this ?
Libtool is really dumb. At configure time, it looks at $CC and tries to find out whether it knows this compiler. If this is a Linux of some sort (which I guess it is) and the Portland compiler, then try ./configure CC=pgcc because libtool should recognize pgcc better than cc. If after that, ./libtool --config | grep "^wl" still shows empty, then you can still try fixing that by editing libtool manually, sed --in-place 's|^wl=.*|wl="-Wl,"|' ./libtool If this is not the Portland compiler on Linux, then Libtool first needs to be ported to that combination. Hope that helps. Cheers, Ralf _______________________________________________ Bug-libtool mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-libtool
