Re: Building XEmacs and modules

Steve Youngs <youngs(a)xemacs.org&gt; wrote: Here's what I did. I got a fresh checkout from CVS. I configured using as close a set of configure flags to yours as I could. The differences are in the GUI (I don't have the NeXT libs), I specified --prefix (I don't have an XEmacs installed under /usr), and I did not use --site-prefixes (both PostgreSQL and LDAP are in the normal places). My build log still does not show the modules auto-autoloads being loaded. Mine goes like this: Wrote /usr/src/xemacs-21.5/lisp/mule/auto-autoloads.el Wrote /usr/src/xemacs-21.5/lisp/mule/auto-autoloads.el Compiling /usr/src/xemacs-21.5/lisp/auto-autoloads.el... Wrote /usr/src/xemacs-21.5/lisp/auto-autoloads.elc Compiling /usr/src/xemacs-21.5/lisp/mule/auto-autoloads.el... Wrote /usr/src/xemacs-21.5/lisp/mule/auto-autoloads.elc Loading /usr/src/xemacs-21.5/lisp/auto-autoloads... Loading /usr/src/xemacs-21.5/lisp/mule/auto-autoloads... Compiling /usr/src/xemacs-21.5/lisp/backquote.el... Wrote /usr/src/xemacs-21.5/lisp/backquote.elc I wonder if this code near the bottom of startup.el has anything to do with it: ;; Hey! Let's use a packages-* function for a non-package purpose! (when (and (not inhibit-autoloads) (featurep 'modules)) (packages-load-package-auto-autoloads module-load-path)) If you comment that out, does the problem go away? If so, this means that your temacs is somehow setting its module-load-path to an installed directory. -- Jerry James http://www.ittc.ku.edu/~james/