Peter B West writes:
I have the rpm of 20.4 on CD, so I installed that, hoping to
bootstrap
from it. Unfortunately, this one seems to have no mule support in it.
I downloaded the mule-base package, and untarred it first into
/usr/local/lib/xemacs/xemacs-packages, then into /usr/lib/xemacs-20.4,
where the rpm installs.
First of all, the Mule of 20.4 and the Mule of 21.0 are entirely
incompatible. You would not be able to bootstrap Mule off 20.4.
The correct place for the mule-base package is somewhere in
/usr/local/lib/xemacs, not xemacs-20.4.
An attempt to `make bindist' in the packages, gives me:
xemacs -no-autoloads -batch -l ../../package-compile.el -- --
add-log.el
Symbol's function definition is void: paths-find-emacs-roots
This sounds like you are specifying your package-path incorrectly.
You are most likely putting xemacs-20.4 ahead of 21.0 on the path.
This is wrong, but there is no documentatino to tell you any of this.
Try this for your package=path configure option. It should work:
--package-path=~/.xemacs::/usr/local/xemacs/xemacs-packages::/usr/lib/xemacs-20.4
Make sure that you get those colons right. If you have your mule
packages in a different directory (/usr/local/xemacs/mule-packages),
it should look like this:
--package-path=~/.xemacs::/usr/local/xemacs/mule-packages:/usr/local/xemacs/xemacs-packages::/usr/lib/xemacs-20.4
This should do for you what you want.
Later, add new packages into /usr/local/xemacs/xemacs-packages, and
they will override the stuff in 20.4.
--
Colin