Hi Hauke,
Short explanation: It is IMHO broken.
Hauke Fath writes:
The problems of leim-1.38, and why the editor build would reach
outside the source tree in the first place, should definitely be
looked at.
The XEmacs build system when it come to the XEmacs binary is, as I get it,
complicated. It tries to do some nifty things that I have got the impression
dates back to the time where system administrators would
change/improve/bug-fix installed elisp-files on a multi user system to the
benefit of their users.
So there once was a requirement that those fixes should be respected when
installing a new version of XEmacs. Hence the binary has some load-path logic
that makes it look beyond the source directory where it is built.
Without looking at your specific case I suspect that this is what is tripping
you. I have similar problems with the build in Gentoo and I have given up on
that. Some situations with the XEmacs build is within Gentoo only possible to
get around by removing packages and install from scratch so that there are no
other files that can confuse the build. And this is even though that Gentoo
builds packages in a sandbox but the XEmacs binary is able to escape that.
This is hardly what users should expected from the Gentoo package manager but
I have failed to solve it. Hence it is what it is.
I think there are some mail discussions around this problem in the XEmacs mail
archives for the interested reader. The bottom line is that changing that code
is believed to be non trivial so no one have had the time nor interest to
solve it.
Possibly one reason is that it only surfaces hard for package managers for
distros? I have never been hit by this problem when building XEmacs and the
packages from the XEmacs Package Source tree.
Yours
--
%% Mats