[mvapich-discuss] Share library error trying to build MVAPICH2
1.4.1 from tarball
David Gunter
dog at lanl.gov
Fri Apr 30 15:26:47 EDT 2010
I am trying to build the latest MVAPICH2 1.4.1 from your tarball. However, I am hitting this bug which Adam Moody reported back on 23 March. Has a solution been found for this yet? I would prefer something that doesn't involve checking out source from your SVN repository as I have yet to be able to get the right mix of autoconf, etc. to create a correct configure script.
On Tue, Mar 23, 2010 at 03:49:08PM -0700, Adam Moody wrote:
> Hello MVAPICH team,
> I was trying to build shared libraries for MVAPICH2-1.4.1 using the
> tarball downloaded from the MVAPICH webpage. I am using the
> following configure command:
>
> ./configure \
> --prefix=/usr/local/tools/mvapich2-intel-debug-1.4.1 \
> --enable-sharedlibs=gcc \
> --enable-f77 --enable-f90 --enable-cxx \
> --enable-fast=O0 --enable-g=dbg \
> --enable-error-checking=runtime --enable-error-messages=all
> --enable-nmpi-as-mpi \
> --enable-debuginfo \
> --with-pmi=slurm --with-pm=no \
> --with-rdma=gen2 --with-ib-include=/usr/include \
> --with-ib-lib=/usr/lib64 \
> --enable-registration-cache \
> --enable-romio --with-file-system=lustre+nfs+ufs \
> --disable-mpe --without-mpe && \
>
> The build seems to complete, but the shared objects are missing from
> the lib directory. When I trace back through the build output, I
> see the following error.
>
> make[2]: Entering directory `/tmp/dpkg-mkdeb.trTLU12767/src/build-mvapich-long-path-hack-enabled-ofa-intel-debug'
> (cd lib && /tmp/dpkg-mkdeb.trTLU12767/src/build-mvapich-long-path-hack-enabled-ofa-intel-debug/src/util/createshlib
> --mode=link -version-info "1:1" -o libmpich.la -rpath
> /usr/local/tools/mvapich2-intel-debug-1.4.1/lib -lpmi -lpthread
> -lrdmacm -libverbs -libumad -lrt -ldflags "" -lpmi -lpthread
> -lrdmacm -libverbs -libumad -lrt )
> /usr/bin/ld: cannot find -ldflags
>
> It seems that createshlib should be stripping the -ldflags as an
> input parameter, but instead it must be passing it on to the linker,
> which then fails to build the shared object.
--
David Gunter
HPC-3: Infrastructure Team
Los Alamos National Laboratory
More information about the mvapich-discuss
mailing list