Jeff, I agree we are not trying to run the binary here, but I am still puzzled here...
Basically, gcc -o a.out foo.o -L/.../hcoll/lib -lhcoll and libhcoll.so depends on libsharp.so (that is in /.../sharp/lib) 1) do you expect this to just work even if the linker has no idea where to find libsharp.so ? 2) if not, how should the linker find libsharp.so without relying on LD_LIBRARY_PATH? Cheers, Gilles On October 15, 2019, at 11:43 PM, "Jeff Squyres (jsquyres) via devel" <devel@lists.open-mpi.org> wrote: You *shouldn't* need to set LD_LIBRARY_PATH, because configure is not trying to actually run the test app that it is compiling. Indeed, it seems that the failure is occurring when it's trying to link (i.e., even if it was trying to run, it seems like the failure is before it would have tried to run). So the new compile line in config.log is: configure:274185: gcc -std=gnu99 -std=gnu99 -o conftest -O3 -DNDEBUG -finline-functions -fno-strict-aliasing -mcx16 -pthread -I/install/u/tjcw/workspace/ompi/build/opal/mca/event/libevent2022/libevent/include -I/install/u/tjcw/workspace/ompi/opal/mca/event/libevent2022/libevent -I/install/u/tjcw/workspace/ompi/opal/mca/event/libevent2022/libevent/include -I/install/u/tjcw/workspace/ompi/build/opal/mca/hwloc/hwloc201/hwloc/include -I/install/u/tjcw/workspace/ompi/opal/mca/hwloc/hwloc201/hwloc/include -I/install/u/tjcw/workspace/ibm_smpi_toucan_ucx/ompibase/dependencies/mofed_400/opt/mellanox/hcoll/include -L/install/u/tjcw/workspace/ibm_smpi_toucan_ucx/ompibase/dependencies/mofed_400/opt/mellanox/sharp/lib -L/install/u/tjcw/workspace/ibm_smpi_toucan_ucx/ompibase/dependencies/mofed_400/opt/mellanox/hcoll/lib conftest.c -lhcoll -lrt -lm -lutil -lz >&5 Meaning: I see the additional -L that you put in there. Just to confirm, the following command returns successfully, right? ls -l /install/u/tjcw/workspace/ibm_smpi_toucan_ucx/ompibase/dependencies/mofed_400/opt/mellanox/sharp/lib/libsharp_coll.so.2 And if that returns successfully, what does this command show? ldd /install/u/tjcw/workspace/ibm_smpi_toucan_ucx/ompibase/dependencies/mofed_400/opt/mellanox/sharp/lib/libsharp_coll.so.2 Finally, there are some other linker errors that are a little concerning, such as: /lib64/libibnetdisc.so.5: undefined reference to `ibd_mkey' /lib64/libibnetdisc.so.5: undefined reference to `get_mkey_by_portid' I'm not sure what those are about / where those symbols will be located. On Oct 15, 2019, at 10:07 AM, Chris Ward <t...@uk.ibm.com> wrote: Adding an appropriate LDFLAGS= didn't help; the revised tarball is here http://tjcw.freeshell.org/ompi-output-2.tar.bz2 . Do I need to specify '-lsharp' to the link command ? If so, how do I do that ? T J (Chris) Ward, IBM Research. Scalable Data-Centric Computing - IBM Spectrum MPI IBM United Kingdom Ltd., Hursley Park, Winchester, Hants, SO21 2JN 011-44-1962-818679 LinkedIn https://www.linkedin.com/in/tjcward/ ResearchGate https://www.researchgate.net/profile/Thomas_Ward16 IBM Research -- Data Centric Systems IBM Supercomputer Marketing IBM Branded Products IBM Branded Swag <Mail Attachment.jpeg> UNIX in the Cloud - Find A Place Where There's Room To Grow, with the original Open Standard. Free Trial Here Today Protein Folding by Supercomputer - BlueMatter Molecular Dynamics package. Data Tables - In-memory key-value store package. Linux on Windows - Virtualisation package. On the Lighthouse ! Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- Jeff Squyres jsquy...@cisco.com
