Folks,
-L/path/to/lib -lfoo will look for the foo library (libfoo.so or
libfoo.a on Linux) in the /path/to/lib directory.
In the case of a dynamic library (e.g. libfoo.so), its dependencies will
*not* be searched in /path/to/lib
(and this is where LD_LIBRARY_PATH helps)
that can be
On Tue, 15 Oct 2019 15:40:24 +
"Jeff Squyres \(jsquyres\) via devel" wrote:
...
> 1) do you expect this to just work even if the linker has no idea
> where to find libsharp.so ?
>
> No, of course not. :-) That's what the additional -L was for.
LIBRARY_PATH is the corresponding variable
That is a VERY old MOFED (couple of years old.) We just released version
4.7.
Josh
On Tue, Oct 15, 2019 at 11:50 AM Chris Ward wrote:
> I'm using a MOFED from file MLNX_OFED_LINUX-4.0-0.0.8.2-rhel7.3-x86_64.tgz
> , this on a machine running RHEL 7.6 . Should I be using a newer MOFED ?
>
>
>
>
I'm using a MOFED from file MLNX_OFED_LINUX-4.0-0.0.8.2-rhel7.3-x86_64.tgz
, this on a machine running RHEL 7.6 . Should I be using a newer MOFED ?
T J (Chris) Ward, IBM Research.
Scalable Data-Centric Computing - IBM Spectrum MPI
IBM United Kingdom Ltd., Hursley Park, Winchester, Hants, SO21
I don't see any other obvious issue here.
Can someone from Mellanox reply?
On Oct 15, 2019, at 10:53 AM, Chris Ward
mailto:t...@uk.ibm.com>> wrote:
-bash-4.2$ ls -l
/install/u/tjcw/workspace/ibm_smpi_toucan_ucx/ompibase/dependencies/mofed_400/opt/mellanox/sharp/lib/libsharp_coll.so.2
On Oct 15, 2019, at 11:05 AM, Gilles GOUAILLARDET via devel
mailto:devel@lists.open-mpi.org>> wrote:
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
Chris,
HCOLL depends on libsharp. What MOFED version are you using? What HCOLL
version are you building against?
Josh
On Tue, Oct 15, 2019 at 11:36 AM Chris Ward via devel <
devel@lists.open-mpi.org> wrote:
> Setting LD_LIBRARY_PATH didn't help; I got the same error.
>
> Is the problem because
Setting LD_LIBRARY_PATH didn't help; I got the same error.
Is the problem because of my MOFED level ? It may be that libsharp.so is
in a different directory, or that libhcoll.so depends on libhsharp.so in a
different way, than with other levels of MOFED.
I just tried building ompi v4.0.x , and
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
-bash-4.2$ ls -l
/install/u/tjcw/workspace/ibm_smpi_toucan_ucx/ompibase/dependencies/mofed_400/opt/mellanox/sharp/lib/libsharp_coll.so.2
lrwxrwxrwx 1 tjcw tjcw 22 Oct 14 08:58
/install/u/tjcw/workspace/ibm_smpi_toucan_ucx/ompibase/dependencies/mofed_400/opt/mellanox/sharp/lib/libsharp_coll.so.2
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
Chris,
I would try to add the directory containing libsharp in your LD_LIBRARY_PATH
Cheers,
Gilles
On October 15, 2019, at 11:08 PM, Chris Ward via devel
wrote:
Adding an appropriate LDFLAGS= didn't help; the revised tarball is here
http://tjcw.freeshell.org/ompi-output-2.tar.bz2 . Do I
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
The sharp libs are in
/install/u/tjcw/workspace/ibm_smpi_toucan_ucx/ompibase/dependencies/mofed_400/opt/mellanox/sharp/lib
. I will an appropriate LDFLAGS to the configure command. Thanks !
Yes, I expected to be using
/install/u/tjcw/workspace/ibm_smpi_toucan_ucx/ompibase/dependencies/bin/ld
Thanks for the info.
Looking at the config.log file, I can see it is trying several different ways
to look for libhcoll. Here's one of them:
configure:274258: gcc -std=gnu99 -std=gnu99 -o conftest -O3 -DNDEBUG
-finline-functions -fno-strict-aliasing -mcx16 -pthread
I have put the tarball requested on my web site here
http://tjcw.freeshell.org/ompi-output.tar.bz2 ; it is too large to be
posted to the mailing list.
It has a 'typescript' from running configure, and the config.log file. My
'configure' command was
../configure
16 matches
Mail list logo
