On Apr 27, 2018, at 12:57 PM, Alastair McKinstry <alastair.mckins...@sceal.ie>
wrote:
>
> Before configure the following is run:
>
> (cd config && autom4te --language=m4sh opal_get_version.m4sh -o
> opal_get_version.sh)
> ./autogen.pl --force
Ah -- you *are* running autogen and re-bootstrapping our tarballs with your own
versions of the GNU Autotools.
What versions are you running of m4, Autoconf, Automake, and Libtool?
Open MPI v3.0.x is built with m4 1.4.17, Autoconf 2.69, Automake 1.15, and
Libtool 2.4.6.
> Then (in this case):
>
> ./configure --build=powerpc64-linux-gnu --prefix=/usr
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man
> --infodir=\${prefix}/share/info
> --sysconfdir=/etc --localstatedir=/var --disable-silent-rules
> --libdir=\${prefix}/lib/powerpc64-linux-gnu
> --libexecdir=\${prefix}/lib/powerpc64-linux-gnu --runstatedir=/run
> --disable-maintainer-mode
> --disable-dependency-tracking --with-verbs
> --with-pmix=/usr/lib/powerpc64-linux-gnu/pmix
> --with-jdk-dir=/usr/lib/jvm/default-java --enable-mpi-java
> --enable-opal-btl-usnic-unit-tests --disable-wrapper-rpath
> --with-libevent=external --enable-mpi-thread-multiple --disable-silent-rules
> --enable-mpi-cxx
> --with-hwloc=/usr/ --with-libltdl=/usr/ --with-devel-headers --with-slurm
> --with-sge --without-tm
> --disable-vt --sysconfdir=/etc/openmpi
> --libdir=\${prefix}/lib/powerpc64-linux-gnu/openmpi/lib
> --includedir=\${prefix}/lib/powerpc64-linux-gnu/openmpi/include
> configure: WARNING: unrecognized options: --disable-maintainer-mode,
> --enable-mpi-thread-multiple, --disable-vt
> checking for perl... perl
This all generally looks fine.
If it really is libtool that is inserting this errant -l without a following
library name, I think we need to know what version of libtool (plus any
Debian-specific patches?) you are using to bootstrap Open MPI's build process,
and see/trace the libtool that is being used to see where that errant -l is
coming from.
If we're not able to get the CI build product, has anyone been able to
reproduce the error manually?
--
Jeff Squyres
jsquy...@cisco.com
