Re: [OMPI devel] 1.10.0rc3 - cannot build libfabic support static?
Paul -- I'm unable to replicate this behavior. But I also don't have the portals libraries. Can you send your configure output, config.log, and full "make V=1" output? Thanks. > On Aug 15, 2015, at 1:17 AM, Paul Hargrove wrote: > > On a Linux/x86-64 system I have configure with > --enable-debug --with-verbs --with-portals4=[path] --with-libfabric=[path] > --with-tm=[path] --disable-io-romio > Configured that way all is fine. However, if I additionally pass > --enable-static --disable-shared > the I see the following build failure: > > /bin/sh ../../../libtool --tag=CC --mode=link gcc -DOTFMERGE_MPI -g -O2 > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs > > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/contrib/vt/vt/../../../.libs > -o otfmerge-mpi otfmerge_mpi-handler.o otfmerge_mpi-otfmerge.o > ../../../otflib/libopen-trace-format.la ../../../otfauxlib/libotfaux.la -lmpi > libtool: link: gcc -DOTFMERGE_MPI -g -O2 -o otfmerge-mpi > otfmerge_mpi-handler.o otfmerge_mpi-otfmerge.o > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs > > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/contrib/vt/vt/../../../.libs > ../../../otflib/.libs/libopen-trace-format.a > ../../../otfauxlib/.libs/libotfaux.a > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a > -L/usr/common/ftg/ptl4/lib -L/usr/syscom/opt/torque/4.1.4/lib > /usr/common/ftg/ptl4/lib/libportals.so /usr/common/ftg/ptl4/lib/libev.so > -libverbs -lrdmacm -lbsd-compat > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/orte/.libs/libopen-rte.a > /usr/syscom/opt/torque/4.1.4/lib/libtorque.so -lxml2 -lz -lcrypto -lssl > -lpthread > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/opal/.libs/libopen-pal.a > -ldl -lrt -lm -lutil -pthread -Wl,-rpath -Wl,/usr/common/ftg/ptl4/lib > -Wl,-rpath -Wl,/usr/syscom/opt/torque/4.1.4/lib -Wl,-rpath > -Wl,/usr/common/ftg/ptl4/lib -Wl,-rpath -Wl,/usr/syscom/opt/torque/4.1.4/lib > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a(mtl_ofi_component.o): > In function `fi_allocinfo': > /usr/common/ftg/libfabric/1.1.0rc2p1/include/rdma/fabric.h:365: undefined > reference to `fi_dupinfo' > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a(mtl_ofi_component.o): > In function `ompi_mtl_ofi_component_init': > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:257: > undefined reference to `fi_getinfo' > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:264: > undefined reference to `fi_strerror' > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:288: > undefined reference to `fi_fabric' > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:292: > undefined reference to `fi_strerror' > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:308: > undefined reference to `fi_strerror' > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:326: > undefined reference to `fi_strerror' > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:347: > undefined reference to `fi_strerror' > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:360: > undefined reference to `fi_strerror' > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a(mtl_ofi_component.o):/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:373: > more undefined references to `fi_strerror' follow > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a(mtl_ofi_component.o): > In function `ompi_mtl_ofi_component_init': > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:404: > undefined reference to `fi_freeinfo' > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:406: > undefined reference to `fi_freeinfo' > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/
Re: [OMPI devel] 1.10.0rc3 - cannot build libfabic support static?
Jeff, I have determined that the problem persists without the --with-portals4. I will send the requested log files and output off-list. -Paul On Wed, Aug 19, 2015 at 12:01 PM, Jeff Squyres (jsquyres) < jsquy...@cisco.com> wrote: > Paul -- > > I'm unable to replicate this behavior. > > But I also don't have the portals libraries. > > Can you send your configure output, config.log, and full "make V=1" output? > > Thanks. > > > > On Aug 15, 2015, at 1:17 AM, Paul Hargrove wrote: > > > > On a Linux/x86-64 system I have configure with > > --enable-debug --with-verbs --with-portals4=[path] > --with-libfabric=[path] --with-tm=[path] --disable-io-romio > > Configured that way all is fine. However, if I additionally pass > > --enable-static --disable-shared > > the I see the following build failure: > > > > /bin/sh ../../../libtool --tag=CC --mode=link gcc -DOTFMERGE_MPI -g > -O2 > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/contrib/vt/vt/../../../.libs > -o otfmerge-mpi otfmerge_mpi-handler.o otfmerge_mpi-otfmerge.o > ../../../otflib/libopen-trace-format.la ../../../otfauxlib/libotfaux.la > -lmpi > > libtool: link: gcc -DOTFMERGE_MPI -g -O2 -o otfmerge-mpi > otfmerge_mpi-handler.o otfmerge_mpi-otfmerge.o > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/contrib/vt/vt/../../../.libs > ../../../otflib/.libs/libopen-trace-format.a > ../../../otfauxlib/.libs/libotfaux.a > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a > -L/usr/common/ftg/ptl4/lib -L/usr/syscom/opt/torque/4.1.4/lib > /usr/common/ftg/ptl4/lib/libportals.so /usr/common/ftg/ptl4/lib/libev.so > -libverbs -lrdmacm -lbsd-compat > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/orte/.libs/libopen-rte.a > /usr/syscom/opt/torque/4.1.4/lib/libtorque.so -lxml2 -lz -lcrypto -lssl > -lpthread > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/opal/.libs/libopen-pal.a > -ldl -lrt -lm -lutil -pthrea > d -Wl,-rpath -Wl,/usr/common/ftg/ptl4/lib -Wl,-rpath > -Wl,/usr/syscom/opt/torque/4.1.4/lib -Wl,-rpath > -Wl,/usr/common/ftg/ptl4/lib -Wl,-rpath -Wl,/usr/syscom/opt/torque/4.1.4/lib > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a(mtl_ofi_component.o): > In function `fi_allocinfo': > > /usr/common/ftg/libfabric/1.1.0rc2p1/include/rdma/fabric.h:365: > undefined reference to `fi_dupinfo' > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a(mtl_ofi_component.o): > In function `ompi_mtl_ofi_component_init': > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:257: > undefined reference to `fi_getinfo' > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:264: > undefined reference to `fi_strerror' > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:288: > undefined reference to `fi_fabric' > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:292: > undefined reference to `fi_strerror' > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:308: > undefined reference to `fi_strerror' > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:326: > undefined reference to `fi_strerror' > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:347: > undefined reference to `fi_strerror' > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:360: > undefined reference to `fi_strerror' > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a(mtl_ofi_component.o):/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:373: > more undefined references to `fi_strerror' follow > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a(mtl_ofi_component.o): > In function `ompi_mtl_ofi_component_init': > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:404: > undefined
Re: [OMPI devel] 1.10.0rc3 - cannot build libfabic support static?
Thanks. It *is* a little odd, though, that the portals flags are showing up in the OFI MTL linker line -- they probably shouldn't be. Todd K. is looking into it. > On Aug 19, 2015, at 4:10 PM, Paul Hargrove wrote: > > Jeff, > > I have determined that the problem persists without the --with-portals4. > I will send the requested log files and output off-list. > > -Paul > > On Wed, Aug 19, 2015 at 12:01 PM, Jeff Squyres (jsquyres) > wrote: > Paul -- > > I'm unable to replicate this behavior. > > But I also don't have the portals libraries. > > Can you send your configure output, config.log, and full "make V=1" output? > > Thanks. > > > > On Aug 15, 2015, at 1:17 AM, Paul Hargrove wrote: > > > > On a Linux/x86-64 system I have configure with > > --enable-debug --with-verbs --with-portals4=[path] --with-libfabric=[path] > > --with-tm=[path] --disable-io-romio > > Configured that way all is fine. However, if I additionally pass > > --enable-static --disable-shared > > the I see the following build failure: > > > > /bin/sh ../../../libtool --tag=CC --mode=link gcc -DOTFMERGE_MPI -g > > -O2 > > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs > > > > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/contrib/vt/vt/../../../.libs > > -o otfmerge-mpi otfmerge_mpi-handler.o otfmerge_mpi-otfmerge.o > > ../../../otflib/libopen-trace-format.la ../../../otfauxlib/libotfaux.la > > -lmpi > > libtool: link: gcc -DOTFMERGE_MPI -g -O2 -o otfmerge-mpi > > otfmerge_mpi-handler.o otfmerge_mpi-otfmerge.o > > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs > > > > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/contrib/vt/vt/../../../.libs > > ../../../otflib/.libs/libopen-trace-format.a > > ../../../otfauxlib/.libs/libotfaux.a > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a > > -L/usr/common/ftg/ptl4/lib -L/usr/syscom/opt/torque/4.1.4/lib > > /usr/common/ftg/ptl4/lib/libportals.so /usr/common/ftg/ptl4/lib/libev.so > > -libverbs -lrdmacm -lbsd-compat > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/orte/.libs/libopen-rte.a > > /usr/syscom/opt/torque/4.1.4/lib/libtorque.so -lxml2 -lz -lcrypto -lssl > > -lpthread > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/opal/.libs/libopen-pal.a > > -ldl -lrt -lm -lutil -pthrea > d -Wl,-rpath -Wl,/usr/common/ftg/ptl4/lib -Wl,-rpath > -Wl,/usr/syscom/opt/torque/4.1.4/lib -Wl,-rpath -Wl,/usr/common/ftg/ptl4/lib > -Wl,-rpath -Wl,/usr/syscom/opt/torque/4.1.4/lib > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a(mtl_ofi_component.o): > > In function `fi_allocinfo': > > /usr/common/ftg/libfabric/1.1.0rc2p1/include/rdma/fabric.h:365: undefined > > reference to `fi_dupinfo' > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a(mtl_ofi_component.o): > > In function `ompi_mtl_ofi_component_init': > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:257: > > undefined reference to `fi_getinfo' > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:264: > > undefined reference to `fi_strerror' > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:288: > > undefined reference to `fi_fabric' > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:292: > > undefined reference to `fi_strerror' > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:308: > > undefined reference to `fi_strerror' > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:326: > > undefined reference to `fi_strerror' > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:347: > > undefined reference to `fi_strerror' > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:360: > > undefined reference to `fi_strerror' > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a(mtl_ofi_component.o):/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:373: > > more undefined references to `fi_strerror' follow > > /global
Re: [OMPI devel] 1.10.0rc3 - cannot build libfabic support static?
Jeff, The linker error that Paul posted isn't an OFI MTL specific linker line. It is the linker line for otfmerge-mpi from VampirTrace package. Portals4 just shows up as an external library the same as OFI or torque. As far as the 3 occurrences of the Portals4 path in that linker line, it breaks down as one -L and two -rpath. I think the -rpath shows up twice because Portals4 depends on libev.so which is installed in the same place as libportals.so and you get one -rpath for each lib. I'll see if that can be deduped. todd On Wed, Aug 19, 2015 at 3:14 PM, Jeff Squyres (jsquyres) wrote: > Thanks. > > It *is* a little odd, though, that the portals flags are showing up in the > OFI MTL linker line -- they probably shouldn't be. Todd K. is looking into > it. > > > > On Aug 19, 2015, at 4:10 PM, Paul Hargrove wrote: > > > > Jeff, > > > > I have determined that the problem persists without the --with-portals4. > > I will send the requested log files and output off-list. > > > > -Paul > > > > On Wed, Aug 19, 2015 at 12:01 PM, Jeff Squyres (jsquyres) < > jsquy...@cisco.com> wrote: > > Paul -- > > > > I'm unable to replicate this behavior. > > > > But I also don't have the portals libraries. > > > > Can you send your configure output, config.log, and full "make V=1" > output? > > > > Thanks. > > > > > > > On Aug 15, 2015, at 1:17 AM, Paul Hargrove wrote: > > > > > > On a Linux/x86-64 system I have configure with > > > --enable-debug --with-verbs --with-portals4=[path] > --with-libfabric=[path] --with-tm=[path] --disable-io-romio > > > Configured that way all is fine. However, if I additionally pass > > > --enable-static --disable-shared > > > the I see the following build failure: > > > > > > /bin/sh ../../../libtool --tag=CC --mode=link gcc -DOTFMERGE_MPI > -g -O2 > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/contrib/vt/vt/../../../.libs > -o otfmerge-mpi otfmerge_mpi-handler.o otfmerge_mpi-otfmerge.o > ../../../otflib/libopen-trace-format.la ../../../otfauxlib/libotfaux.la > -lmpi > > > libtool: link: gcc -DOTFMERGE_MPI -g -O2 -o otfmerge-mpi > otfmerge_mpi-handler.o otfmerge_mpi-otfmerge.o > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs > -L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/contrib/vt/vt/../../../.libs > ../../../otflib/.libs/libopen-trace-format.a > ../../../otfauxlib/.libs/libotfaux.a > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a > -L/usr/common/ftg/ptl4/lib -L/usr/syscom/opt/torque/4.1.4/lib > /usr/common/ftg/ptl4/lib/libportals.so /usr/common/ftg/ptl4/lib/libev.so > -libverbs -lrdmacm -lbsd-compat > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/orte/.libs/libopen-rte.a > /usr/syscom/opt/torque/4.1.4/lib/libtorque.so -lxml2 -lz -lcrypto -lssl > -lpthread > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/opal/.libs/libopen-pal.a > -ldl -lrt -lm -lutil -pthr > ea > > d -Wl,-rpath -Wl,/usr/common/ftg/ptl4/lib -Wl,-rpath > -Wl,/usr/syscom/opt/torque/4.1.4/lib -Wl,-rpath > -Wl,/usr/common/ftg/ptl4/lib -Wl,-rpath -Wl,/usr/syscom/opt/torque/4.1.4/lib > > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a(mtl_ofi_component.o): > In function `fi_allocinfo': > > > /usr/common/ftg/libfabric/1.1.0rc2p1/include/rdma/fabric.h:365: > undefined reference to `fi_dupinfo' > > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/BLD/ompi/.libs/libmpi.a(mtl_ofi_component.o): > In function `ompi_mtl_ofi_component_init': > > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:257: > undefined reference to `fi_getinfo' > > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:264: > undefined reference to `fi_strerror' > > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:288: > undefined reference to `fi_fabric' > > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:292: > undefined reference to `fi_strerror' > > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:308: > undefined reference to `fi_strerror' > > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x86_64-static/openmpi-1.10.0rc3/ompi/mca/mtl/ofi/mtl_ofi_component.c:326: > undefined reference to `fi_strerror' > > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc3-linux-x
Re: [OMPI devel] 1.10.0rc3 - cannot build libfabic support static?
On Aug 19, 2015, at 5:01 PM, Todd Kordenbrock wrote: > > Jeff, > > The linker error that Paul posted isn't an OFI MTL specific linker line. It > is the linker line for otfmerge-mpi from VampirTrace package. Portals4 just > shows up as an external library the same as OFI or torque. Ah, right you are -- and those are there because of --enable-static --disable-shared. So: all is good there. > As far as the 3 occurrences of the Portals4 path in that linker line, it > breaks down as one -L and two -rpath. I think the -rpath shows up twice > because Portals4 depends on libev.so which is installed in the same place as > libportals.so and you get one -rpath for each lib. I'll see if that can be > deduped. K. Not a huge deal, but would be nice to fix up. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
