Re: Question about mule compiled elisp files
James LewisMoss <dres(a)ioa.com> writes:
Is it safe to use mule compiled elisp files with a non-mule binary?
Yes, if the source was plain ascii.
No, otherwise.
First is that trying to use jka-compr gives an error like
coding-system-for-read undefined.
This is a bug in the jka-compr package. There is patch around for
ages, but for some reason we haven't had a package release release for
some months.
These are really urgent patches that are prime candidates for your
.diff section
This fixes the jka-compr bug
http://www.xemacs.org/list-archives/xemacs-patches/9908/msg00013.html
This fixes a similar problem in calendar.el
http://www.xemacs.org/list-archives/xemacs-patches/9908/msg00063.html
This fixes an equally stupid bug with ps-print
http://www.xemacs.org/list-archives/xemacs-patches/9907/msg00053.html
The other is that when starting a non-mule binary the warnings
(1) (warning/warning) Autoload error in:
/usr/share/xemacs21/mule-packages/lisp/skk/auto-autoloads:
Cannot open load file: mule
(2) (warning/warning) Autoload error in:
/usr/share/xemacs21/mule-packages/lisp/lookup/auto-autoloads:
Cannot open load file: mule
This is wrong. The package-path should NOT contain mule-packages for a
non-mule build. Are you setting the package-path explicitly?
Jan
P.S. I suggest you either use the mainline CVS or weight for .8 as
those contain some patches tailor made for you (the Linux dumping
architecture problems that I sent you a patch for and a fix work
around a bug in the recent glibc version that potato uses)