I'm noticing on an `emerge -Du world that when something comes along
that needs to be byte compiled by emacs it causes a failure and errors
out.

I'm pretty sure it is because I have a built from source install of
emacs (not emerged) on /usr/local .  What appears to be happing is
that my PREFIX/share/emacs/site-lisp/site-start.el is being loaded and
interfering with what emerge expects from emacs.

This can only happen if emacs is being run WITHOUT the:
   -no-site-file
flag.

One would expect emacs to be called like:
  emacs -q -no-site-file
for any usage in emerge.

That would allow users to have there own customized emacs install
whether thru emerge or not.

Is the way emerge calls emacs something I can set myself? or is it
hard programmed somewhere?

--
[email protected] mailing list

Reply via email to