nbecker(a)fred.net writes:
I don't know if anyone noticed my previous post on this subject.
I noticed it, and I disagree with it.
As I recall, it was removed because it can cause severe problems.
If an rpath is compiled in to an executable, that is later run in a
different environment, the referenced rpath could contain references
to NFS mounted stuff that is no longer valid, causing severe startup
delays.
I would expect XEmacs to notice the location of libraries and use it.
If I move the libraries and XEmacs malfunctions because of that, I
can't really blame it. Hardcoding library paths in the binary is IMO
much better than the alternative, which is building an XEmacs that
doesn't work.
And it was never removed, except from Linux.