On Thu, 14 Mar 2002, Ben Wing wrote:
"Stephen J. Turnbull" wrote:
>
> >>>>> "Simon" == Simon Josefsson <jas(a)extundo.com>
writes:
>
> Simon> Loading unicode.el...*** Error in XEmacs initialization
> Simon> (void-function define-ccl-program)
>
> Try EMACSLOADPATH=`pwd`/lisp:`pwd`/mule make. I have a patch pending,
> but I don't know if it's TheRaightThang[tm].
actually, i've been spending the last few hours trying to do this right
-- and of course discovering lots of other really cruddy startup code
that needs cleaning.
anyway, there is more than one possible path to take. the one i'm
taking is to disable entirely all recognition of packages when compiling
xemacs. this requires another command-line flag -- no-autoloads isn't
enough because the shadowing file still sits on the load path.
i think this is the right thing -- xemacs should be able to compile
without packages and have the packages added later. compiling without
packages ensures that nothing specific to the compiler's package
environment gets stuck somewhere in the compiled xemacs, thence to cause
problems with different packages.
my only concern is people adding other stuff to dump, which is dependent
on packages. is this a real concern that i should worry about?
Simply adding EMACSLOADPATH=`pwd`/lisp:`pwd`/mule to the Makefile seems
like a solution. If people want to dump with external stuff, they have to
fix the load path and load their lisp themselves.