Jean-Jacques, pray send a copy of your answer to [EMAIL PROTECTED], as I do. I am not the maintainer of the package, just an interested and somewhat experienced bystander, and the mails should really get delivered to the maintainer, and be archived in the BTS.
Apropos experienced, I must admit that the last mails we exchanged were more about me getting (again) used to the way the auctex setup is done upon installation, but unfortunately it didn't tell me much about the problems that arise here. >From the log you sent I learned - that it is not surprising that there is no 50auctex.el file in /etc/emacs21/site-start.d/, because this file is only created after the emacs-package-install script has completed successfully. - for the same reason, it is not surprising that when you start emacs, it doesn't find any auctex files; the necessary additions to the load-path would be done in the 50auctex.el file. So we are back to the question "why does the emacs-package-install script fail?". First it changes to the directory where the auctex-lisp files are, then it successfully calls ./configure, but it fails when it tries to call "make install-lisp install-contrib". The information about this is in the Compilation.log you sent earlier. There it says: > Type "make" at the prompt to build AUCTeX > /usr/bin/emacs21 -batch -q -no-site-file -l lpath.el -f batch-byte-compile > context-en.el > While compiling toplevel forms in file > /usr/share/emacs/site-lisp/auctex/context-en.el: > !! Symbol's function definition is void ((TeX-mode-specific-command-menu)) > Done > make: *** [context-en.elc] Error 1 I just tried this here, byte-compilation should work without problems, irrespective of the order in which files are byte compiled. So to further debug this, I'd like you to do the following: $ cd /usr/share/emacs/site-lisp/auctex/ $ su # ./configure --disable-build-dir-test --prefix=/usr/ --with-emacs=emacs21 --with-lispdir=/usr/share/emacs21/site-lisp/ --with-auto-dir=/var/lib/auctex/emacs21 # /usr/bin/emacs21 -q -no-site-file -l lpath.el (you might need to add the option "-nw" if it says it cannot open a display or a similar error message). Then do M-x toggle-debug-on-error RET M-x byte-compile-file RET context-en.el RET And tell us what you get; especially the contents of the backtrace and Messages buffers are interesting. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
