Re: mule question

intro: "JAT" == John A Turner <turner(a)blueskystudios.com&gt; writes: JAT> I've always build w/o mule, but a colleague needs mule he's building his JAT> own executable, but I thought we might as well share the same packages JAT> tree, since we saw that the mule-sumo tarball just has the extra mule JAT> stuff in it - it un-tars nicely into its own mule-packages subdir in JAT> lib/xemacs, parallel to the xemacs-packages I was already using JAT> but now when I start my non-mule xemacs I see these warnings: JAT> (1) (warning/warning) Autoload error in: JAT> /usr/net/rnd/lib/xemacs/mule-packages/lisp/skk/auto-autoloads: JAT> Cannot open load file: mule JAT> (2) (warning/warning) Autoload error in: JAT> /usr/net/rnd/lib/xemacs/mule-packages/lisp/lookup/auto-autoloads: JAT> Cannot open load file: mule JAT> is this just one of those "don't do that" things, or should this be ok? JAT> that is, should we just ignore the warnings, or do they indicate some JAT> deeper badness? Don't worry, these warnings indicate that your non-mule xemacs browses through `skk' and `lookup', mule-supporting packages. If it disturbs you than rebuild your xemacs explicitly setting where to look for packages: configure --package-path=/usr/local/lib/xemacs/xemacs-packages Nick.