Closed stepeos closed 1 year ago
Since you're installing from source and have a custom install prefix, it may be possible that CMake is being picky about this. I am also surprised it worked for you before without the LD_PRELOAD
or the CMAKE_PREFIX_PATH
variables including the custom install directory.
Can you try building from scratch again in a new directory (e.g. build2) and report back on whether you still have this issue? You may want to delete the current install by running xargs rm -rf < install_manifest.txt
in your current build folder.
Since you're installing from source and have a custom install prefix, it may be possible that CMake is being picky about this. I am also surprised it worked for you before without the
LD_PRELOAD
or theCMAKE_PREFIX_PATH
variables including the custom install directory.Can you try building from scratch again in a new directory (e.g. build2) and report back on whether you still have this issue? You may want to delete the current install by running
xargs rm -rf < install_manifest.txt
in your current build folder.
This fixed the issue? That is very strange. Thanks for the help.
Description
I successfully compiled and linked my ./my_program using cmake. Attempting to run
./my_program
results in:I can find said shared library object in the local installation directory. However the output of
ldd
suggests the library file cannot be found.Steps to reproduce
I have encountered an error when upgrading from 4.1.1 to 4.2, using the release zip from here. After following the installation instructions
Then in my CMakeLists.txt I create a shared library object:
Expected behavior
Environment
I am using Ubuntu focal, latest with the following configuration:
Additional information
A temporary fix is to add the entry to the
.bashrc
:This fixes the problem temporarily, so does this commentator's suggestion.
I am surprised, that the
make check
command finished successfully, so I wonder whether the problem stems from my CMakeLists.txt?