Re: [Bug-AUCTeX] 2005-05-11; XEmacs exits during make

[David Kastrup]

Ralf Angeli <address@hidden> writes:

> XEmacs exits during make when the autoloads are being generated:
>
> --8<---------------cut here---------------start------------->8---
> # make && make install
> test X/usr/share/xemacs21/site-packages != Xno || \
> rm -f auto-loads.el ; \
> /usr/bin/xemacs -batch -q -no-site-file -no-init-file -l lpath.el --eval 
> '(let ((generated-autoload-file (expand-file-name "auto-loads.el"))) (mapcar 
> (function update-file-autoloads) command-line-args-left) 
> (save-buffers-kill-emacs t))' tex.el tex-buf.el tex-style.el latex.el 
> tex-info.el texmathp.el multi-prompt.el tex-mik.el font-latex.el tex-font.el 
> context.el context-en.el context-nl.el tex-fold.el toolbar-x.el tex-bar.el; \
> test -r auto-loads.el || \
> echo ";; Auto-generated part of tex-site.el" > auto-loads.el ; \
> echo "
>       " >> auto-loads.el ; \
> /usr/bin/xemacs -batch -q -no-site-file -no-init-file -l lpath.el --eval 
> '(let ((generated-autoload-file (expand-file-name "auto-loads.el"))) (mapcar 
> (function update-file-autoloads) command-line-args-left) 
> (save-buffers-kill-emacs t))' tex.el tex-buf.el tex-style.el latex.el 
> tex-info.el texmathp.el multi-prompt.el tex-mik.el font-latex.el tex-font.el 
> context.el context-en.el context-nl.el tex-fold.el toolbar-x.el tex-bar.el
> End of file or stream: #<buffer "auto-loads.el">
> xemacs exiting
> .
> (No files need saving)
> cat tex-site.el.out >tex-site.el
> test X/usr/share/xemacs21/site-packages != Xno || cat auto-loads.el 
> >>tex-site.el
> echo "(provide 'tex-site)" >>tex-site.el ; \
> test X/usr/share/xemacs21/site-packages != Xno || echo ";;; tex-site.el ends 
> here" >>tex-site.el
> [...]
> --8<---------------cut here---------------end--------------->8---
>
> Note the "xemacs exiting" message.  The make and make install process
> seems to carry on normally despite this event.  I don't really know if
> this is a bug.

If the file actually contains the autoloads, it would appear that
everything is in order.  Notice that the above code tries _twice_ to
generate the autoloads, with different starting values of the autoload
file.  This proved necessary since Emacs and XEmacs have incompatible
ways of generating autoloads.

So it is perfectly possible that the first attempt at generating
autoloads fails, and only the second attempt succeeds.

Does the resulting file actually contain autoloads?  If it does,
things work like intended.

Not pretty, but as intended.  Compared to other workarounds, this
could be worse.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum