Question about mule compiled elisp files

Is it safe to use mule compiled elisp files with a non-mule binary? I've hit a couple of things that make me think it's not quite right (but close). First is that trying to use jka-compr gives an error like coding-system-for-read undefined. If I set that to nil then I get file-coding-system-alist undefined, but the following bit of code lets jka-compr work just fine. (as far as I can tell) (defvar file-coding-system-alist nil) (defvar coding-system-for-read nil) (require 'jka-compr) (jka-compr-install) 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 actually from a report from a debian user, but I think I've seen this before. (just tested it and I do see this at startup.)) Again it looks like it is causing no problems, but I wanted to ask in case there were things I should watch out for. Oh and just so you understand how things are compiled: 1) configure for a mule, canna, wnn setup. 2) compile the binary. 3) compile the elisp 4) configure for a mule (no input methods but xim) 5) compile the binary 6) configure for a non-mule 7) compile the binary These are then installed together (with each binary being xemacs-21.1.7-{mule,mule-canna-wnn,nomule} and doc files in /usr/lib/xemacs-21.1.7/i386-debian-linux/{mule,mule-canna-wnn,nomule}/DOC). Thanks Jim -- ＠James LewisMoss <dres(a)ioa.com&gt; | Blessed Be! ＠ http://www.ioa.com/~dres | Linux is kewl! ＠"Argue for your limitations and sure enough, they're yours." Bach