Re: Why does ltmain.sh::temp_rpath not need the same system lib considerations?

On Thu, 16 Feb 2017, Nish Aravamudan wrote:
>
> I do not believe so, the tests (heimdal self-tests) are run via a
> Makefile target which calls the generated wrapper script(s).

Normally if you call the generated wrapper scripts, things should be 
ok, as long as the linkage was correct in the first place.

> I really appreciate the response! From what I can tell, though, the
> temp_rpath variable is not actually used to compile/link anything, it's
> only used for the wrapper script generator. And I don't understand how
> it would be correct for an explicit LD_LIBRARY_PATH specification (as
> done by the wrapper generator) to have the system library path anywhere
> before the end of the list. Otherwise, if any of the required library
> dependencies are installed, the somewhat arbitrary set before the system
> library path in LD_LIBRARY_PATH will use the built libraries and the
> somewhat arbitrary set after the system library path in LD_LIBRARY_PATH
> will use the system libraries without any indication of a problem -- and
> it becomes rather murky what is actually being tested.

I don't think that it is normal or ok to have the system library path 
in the list at all.  Perhaps libtool is not determining that the path 
is a system library path.

Check the output of './libtool --config'.  Particularly, 
sys_lib_dlsearch_path_spec.  Maybe it is wrong.

Bob
-- 
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

_______________________________________________
https://lists.gnu.org/mailman/listinfo/libtool