On Mon, Nov 28, 2011 at 23:30, Andy Spencer <[email protected]> wrote:
> This seems to be caused by libtool adding a -rpath flag which forces the > application to use the /usr/lib64 version provided by mesa even though > ld.so.conf has been properly configured to use the nvidia version. I ran into essentially the same problem on Scientific Linux 6, essentially libtool sometimes incorrectly determines the system library paths. I imagine if you look at the sys_lib_dlsearch_path_spec variable within the libtool script it will state that /usr/lib is a system library path and not /usr/lib64. Therefore libtool will assume it needs to pass /usr/lib64 on the command line thereby leading to this linking problem. I raised this question a week or so ago and the workaround suggested was to set: lt_cv_sys_lib_dlsearch_path_spec="/lib64 /usr/lib64" during configure, this overrides the paths found by libtool and solved the linking problem for me. Unfortunately this is a hack and ignores any paths specified in ld.so.conf so you may need to tweak this accordingly. Hope this is of some help. Cheers Adam _______________________________________________ https://lists.gnu.org/mailman/listinfo/libtool
