Martin Buchholz <martin(a)xemacs.org> writes:
On non-Linux platforms, we build XEmacs using a runpath that is
computed from the link path.
[...]
I've generally felt that we should be doing this even on
platforms
like Linux where /etc/ld.so.conf gives us the runtime library search
path. However, Steve was strong in his insistence that we don't
specify a run-path via -R, and that we let /etc/ld.so.conf win out.
I agree with your view -- in fact, I was the one who bitched about the
problem under Solaris which I used at the time.
However, Steve's technical argument against this method was that Linux
makes use of ld.so.conf to ensure old versions of executables for
libraries that need them. This way a libc5 program "knows" that old
libraries are in a "libc5-compat" directory. If we hardcode the
runtime library path into the executable, we lose that capability,
don't we?