Mats Lidell writes:
>>>>> Mats Lidell <matsl(a)xemacs.org> writes:
Sorry for following up on my own post but I really need som help on
this one.
> I'm afraid that the problem is worse than that. [...]
> 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...
What's happening is that merely loading "startup" changes load-path.
I see that in my build, but for me it changes load-path to something
harmless (it adds the symlink $blddir/lisp -> $srcdir/lisp).
Resetting load-path at dump time is apparently intentional; see the
comment on the call to `startup-setup-paths' around line 1710 in
startup.el. I don't have time to look into it further today, and
probably not until the weekend. You could try pinging Mike.
Did you post your Installation file? If not, would you do so? I
suspect you have an explicit setting for lisp-directory. Try to avoid
that; setting --datarootdir=PARENT-OF-LISP should be sufficient, and
probably would work around this problem.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta