We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I ran into trouble caused by libtool adding /usr/lib64 to the rpath of a library.
/usr/lib64
sys_lib_dlsearch_path_spec seems to be intended to avoid adding default paths to rpath. For Linux (linux-gnu) it is set here:
sys_lib_dlsearch_path_spec
libtool/m4/libtool.m4
Line 2956 in 5586070
However this misses /usr/lib64 and only adds /usr/lib
I don't see that folder in ldconf.so but in ld --verbose:
ld --verbose
$ ld --verbose | grep SEARCH_DIR SEARCH_DIR("=/usr/x86_64-redhat-linux/lib64"); SEARCH_DIR("=/usr/lib64"); SEARCH_DIR("=/usr/local/lib64"); SEARCH_DIR("=/lib64"); SEARCH_DIR("=/usr/x86_64-redhat-linux/lib"); SEARCH_DIR("=/usr/local/lib"); SEARCH_DIR("=/lib"); SEARCH_DIR("=/usr/lib");
Is that intentional or an oversight? Can this be fixed/workarounded without changing the source?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I ran into trouble caused by libtool adding
/usr/lib64
to the rpath of a library.sys_lib_dlsearch_path_spec
seems to be intended to avoid adding default paths to rpath. For Linux (linux-gnu) it is set here:libtool/m4/libtool.m4
Line 2956 in 5586070
However this misses /usr/lib64 and only adds /usr/lib
I don't see that folder in ldconf.so but in
ld --verbose
:Is that intentional or an oversight?
Can this be fixed/workarounded without changing the source?
The text was updated successfully, but these errors were encountered: