Brice Goglin, le Tue 23 Apr 2013 19:12:08 +0200, a Ã©crit :
> I assume that libtool doesn't add a rpath when you install in standard
Yes, it's doing stuff to detect with paths are actually already in the
standard search dirs.
> If /usr/lib64 is the default path for 64bits libs on Fedora, shouldn't somebody
> take care of removing the corresponding rpath too?
libtool should be already doing that.
> This is likely related (but the reversed case) to the comment about Fedora in
> http://wiki.debian.org/RpathIssue. One link on that page says that rerunning
> libtoolize before configure may help. Can you try that? (maybe compare the new
> libtool script with the one from the hwloc tarball to check that some lib64
> things appeared?)
> â¡ If the application uses a local copy of libtool, add the following
> lines to the spec afterÂ %configure:=> it will make tests FAIL (without
> this change, it runs just fine - all tests are PASSED)
> FAIL: test-hwloc-annotate.sh
> FAIL: test-hwloc-assembler.sh
> PASS: test-hwloc-calc.sh
> PASS: test-hwloc-distances.sh
> PASS: test-hwloc-distrib.sh
> FAIL: test-hwloc-info.sh
> I am not sure why some fail while the other succeed. You may need to set
> LD_LIBRARY_PATH to fix this?
The libtool script is supposed to automatically add it.
It would probably be worth running by hand to see what actually fails.