CCL related failures in the package tree.

Malcolm Purvis malcolmp at xemacs.org
Thu Aug 2 08:56:41 EDT 2007


>>>>> "Michael" == Michael Sperber <sperber at informatik.uni-tuebingen.de> writes:

Michael> Aidan Kehoe <kehoea at parhasard.net> writes:

Michael> What does

Michael> (startup-find-load-path)

Michael> return?

$ xemacs -no-autoloads -vanilla -batch -eval '(message "%s" (startup-find-load-path))'

(/Users/malcolmp/prefix/share/xemacs/site-lisp/
/Users/malcolmp/prefix/share/xemacs-21.5-b28/lisp/mule/
/Users/malcolmp/prefix/share/xemacs-21.5-b28/lisp/)

So the directory is present when XEmacs starts, but isn't there during
package compilation.

Expanding on what I said in my last message, it looks like the offending
code is this from package-compile.el:
 
(let ((depth (cond
               ;; #### All hail Mr. Preprocessor!
               ;; OK, OK, his code is under development; FIXME when it's done. 
              ((boundp 'paths-load-path-depth) ; XEmacs 21.1 
               paths-load-path-depth) 
              ((boundp 'paths-core-load-path-depth) ; XEmacs > 21.2.41 
               paths-core-load-path-depth) 
              (t (error "Somebody has been messing with paths-find-*!"))))) 
  (setq load-path (paths-find-recursive-load-path (list lisp-directory) 
                                                  depth))) 

What then is the right way to reset the load-path to only refer to the
core and mule directories?

Malcolm

-- 
		     Malcolm Purvis <malcolmp at xemacs.org>



More information about the XEmacs-Beta mailing list