Le 24/04/2013 00:35, Paul Hargrove a écrit :
> I took a look at libtool.m4 and find that
> the sys_lib_dlsearch_path_spec value is HARDCODED as part of big
> "case $host_os in". That is why the autoreconf resolves the problem -
> the distro maintainers have customized libtool.m4 appropriately.
>
> Other than instructing folks to autoreconf, I don't see a "clean" fix
> for this issue.
>

Ok, thanks. So our configure indeed generates libtool script that
depends on where the tarball was generated. That's a bit disturbing.

[snip]

It is not quite as you describe because I was talking about Fedora's libtool.m4 doing the hardcoding.

The libtool.m4 logic that is distributed with hwloc *tries* to perform a configure probe to determine the dynamic lib search path.

Unfortunately, that probe isn't smart enough to get the right answer on all Linux distros.

So, the libtool.m4 from Fedora is the one I see hardcoding the correct answer.

Again: libtool in the official tarball of hwloc-1.7 does NOT do something as horrible as hardcode the wrong answer from the distro where one built the tarball (but it probably would it you built the tarball on Fedora).

It appears somebody has been bugging the libtool developers about this since June 2010: