You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When linking with libtool against HPC-X provided in the marketplace image the build fails due to a hardcoded path in the dependency_libs metadata of the libtool archive files included with HPC-X. Since this path (/hpc/local/oss/...) does not exist in the image, the linker cannot find the target .la files required to complete the dependency resolution which causes the build to fail.
Here is a list of all the .la files in HPC-X referencing the /hpc/local/oss/... path:
I'm hitting the same issue building parallel netcdf against the marketplace hpcx:
653 libtool: warning: library '/opt/hpcx-v2.8.3-gcc-MLNX_OFED_LINUX-5.2-2.2.3.0-redh
at7.9-x86_64/ompi/lib/libmpi_usempif08.la' was moved.
654 /bin/grep: /hpc/local/oss/gcc-9.2.0/lib/../lib64/libgfortran.la: No such file or
directory
655 /bin/sed: can't read /hpc/local/oss/gcc-9.2.0/lib/../lib64/libgfortran.la: No su
ch file or directory
I tried Davide's workaround mentioned above and removed /opt/hpcx-v2.8.3-gcc-MLNX_OFED_LINUX-5.2-2.2.3.0-redhat7.9-x86_64/ompi/lib/*.la and everything links ok now.
When linking with libtool against HPC-X provided in the marketplace image the build fails due to a hardcoded path in the
dependency_libs
metadata of the libtool archive files included with HPC-X. Since this path (/hpc/local/oss/...
) does not exist in the image, the linker cannot find the target.la
files required to complete the dependency resolution which causes the build to fail.Here is a list of all the
.la
files in HPC-X referencing the/hpc/local/oss/...
path:Two potential solutions:
.la
files and let the linker resolve the dependencies at link timeThe second solution would be preferred in order to allow customer to correctly link against any library, not only the ones provided in the HPC stack.
The text was updated successfully, but these errors were encountered: