>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
is actually false for repeated builds from the same source. If you
do
a Mule build in-tree, then a no-Mule build, the same thing will
happen. [...]
Agreed. Removing the elc-files is just fix that does not solve the
general problem that the you should be able to reconfigure and just
make and get a proper result.
I don't know if there is some way to tie a (re)configure to some
action or if some state-file with whether last build was a mule-build
or not is the way to go. Suggestions are welcome.
That's the best option for distro builds, of course, [...]
I'm afraid that the problem is worse than that. It seems like that
during the build the load of startup.el changes the path so that the
build after that starts to load from
/usr/share/xemacs-21.5-b33/lisp/... ouch!
Excerpt from build log:
Loading
/var/tmp/portage/app-editors/xemacs-21.5.33/work/xemacs-21.5.33/lisp/modeline.elc...
Loading
/var/tmp/portage/app-editors/xemacs-21.5.33/work/xemacs-21.5.33/lisp/cus-file.elc...
Loading
/var/tmp/portage/app-editors/xemacs-21.5.33/work/xemacs-21.5.33/lisp/startup.elc...
Loading /usr/share/xemacs-21.5-b33/lisp/misc.elc...
Loading /usr/share/xemacs-21.5-b33/lisp/loadhist.elc...
Loading /usr/share/xemacs-21.5-b33/lisp/files.elc...
...
Scary isn't it. During the build of the binary we should only load
files from the sources and not look around in what is installed
on the machine, right?
Suggestions are welcome on how to solve this.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta