Oops!  I spoke too soon.

The configuration with "--with-libfabric=[path] --enable-static
--disable-shared" is still causing problems.
Previously (http://www.open-mpi.org/community/lists/devel/2015/08/17752.php)
I was seeing a failure to link otfmerge-mpi during the build of Open MPI.
Now I am instead seeing the (essentially identical) linker errors when
compiling the examples:

$ mpicc -g    hello_c.c   -o hello_c
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/INST/lib/libmpi.a(mtl_ofi_component.o):
In function
`fi_allocinfo':/usr/common/ftg/libfabric/1.1.0/include/rdma/fabric.h:366:
undefined reference to
`fi_dupinfo'/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/INST/lib/libmpi.a(mtl_ofi_component.o):
In function `ompi_mtl_ofi_component_init':
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/mtl/ofi/mtl_ofi_component.c:260:
undefined reference to `fi_getinfo'
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/mtl/ofi/mtl_ofi_component.c:267:
undefined reference to
`fi_strerror'/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/mtl/ofi/mtl_ofi_component.c:291:
undefined reference to `fi_fabric'
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/mtl/ofi/mtl_ofi_component.c:295:
undefined reference to `fi_strerror'
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/mtl/ofi/mtl_ofi_component.c:311:
undefined reference to `fi_strerror'
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/mtl/ofi/mtl_ofi_component.c:329:
undefined reference to
`fi_strerror'/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/mtl/ofi/mtl_ofi_component.c:350:
undefined reference to `fi_strerror'
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/mtl/ofi/mtl_ofi_component.c:363:
undefined reference to `fi_strerror'
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/INST/lib/libmpi.a(mtl_ofi_compone
nt.o):/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/
mtl/ofi/mtl_ofi_component.c:376: more undefined references to `fi_strerror'
follow
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/INST/lib/libmpi.a(mtl_ofi_component.o):
In function `ompi_mtl_ofi_component_init':
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/mtl/ofi/mtl_ofi_component.c:407:
undefined reference to `fi_freeinfo'
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/mtl/ofi/mtl_ofi_component.c:409:
undefined reference to `fi_freeinfo'
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/mtl/ofi/mtl_ofi_component.c:418:
undefined reference to `fi_strerror'
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/mtl/ofi/mtl_ofi_component.c:457:
undefined reference to `fi_freeinfo'
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/openmpi-1.10.0rc4/ompi/mca/mtl/ofi/mtl_ofi_component.c:460:
undefined reference to `fi_freeinfo'
/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/INST/lib/libmpi.a(mtl_ofi.o):
In function `ompi_mtl_ofi_del_procs':
[and many more]

Since this is certainly not my first rodeo, I'll jump right to the --show
output:

$ mpicc --show -g hello_c.c -o hello_c'
gcc -g hello_c.c -o hello_c
-I/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/INST/include
-pthread -L/usr/syscom/opt/torque/4.1.4/lib -Wl,-rpath
-Wl,/usr/syscom/opt/torque/4.1.4/lib -Wl,-rpath
-Wl,/usr/syscom/opt/torque/4.1.4/lib -Wl,-rpath
-Wl,/usr/syscom/opt/torque/4.1.4/lib -L/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,/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/INST/lib
-Wl,--enable-new-dtags
-L/global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-1.10.0rc4-linux-x86_64-static/INST/lib
-lmpi -lopen-rte -lopen-pal -lm -ldl -lrt -ltorque -libverbs -lportals
-lrdmacm -lutil

I can send config.log and configure output off-list to whomever asks.

-Paul

On Sat, Aug 22, 2015 at 3:59 PM, Paul Hargrove <phhargr...@lbl.gov> wrote:

> At this point I can confirm that all of my configurations that experienced
> failures with rc3 have passed with rc4.
> I will report again after all tests have completed (likely on Sunday).
>
> -Paul
>
> On Sat, Aug 22, 2015 at 1:46 PM, Ralph Castain <r...@open-mpi.org> wrote:
>
>> Final release candidate for v1.10.0:
>>
>> http://www.open-mpi.org/software/ompi/v1.10/
>>
>> Please let me know immediately if you see a problem - scheduled for
>> release after the Tues telecon
>>
>> Ralph
>>
>> _______________________________________________
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2015/08/17790.php
>>
>
>
>
> --
> Paul H. Hargrove                          phhargr...@lbl.gov
> Computer Languages & Systems Software (CLaSS) Group
> Computer Science Department               Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900
>



-- 
Paul H. Hargrove                          phhargr...@lbl.gov
Computer Languages & Systems Software (CLaSS) Group
Computer Science Department               Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900

Reply via email to