From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 47394@debbugs.gnu.org
Subject: bug#47394: 27.2; admin.el:make-manuals infloops on HTML manuals
Date: Thu, 25 Mar 2021 22:17:22 +0200 [thread overview]
Message-ID: <83ft0jq97x.fsf@gnu.org> (raw)
In-Reply-To: <1qczvnkoc0.fsf@fencepost.gnu.org> (message from Glenn Morris on Thu, 25 Mar 2021 15:47:27 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: 47394@debbugs.gnu.org
> Date: Thu, 25 Mar 2021 15:47:27 -0400
>
> Eli Zaretskii wrote:
>
> > Removing old name: no such file or directory,
> > /home/e/eliz/git/emacs/pretest/manual/ps/eintr.dvi
> > make-manuals: error running make-manuals
> >
> > What does it mean? that TeX barfed producing eintr.dvi?
>
> Probably. Indeed this fails on fencepost:
>
> texi2dvi -I ../emacs -I ../misc emacs-lisp-intro.texi -o eintr.dvi
Output written on emacs-lisp-intro.dvi (272 pages, 986064 bytes).
Transcript written on emacs-lisp-intro.log.
/home/e/eliz/bin/texi2dvi: etex exited with bad status, quitting. <<<<<<<<<
Does anyone have any idea what causes this? The only messages that
could mean trouble are:
./emacs-lisp-intro.texi:9527: epsf.tex not found, images will be ignored.
@image ...f.tex not found, images will be ignored}
@global @warnednoepsftrue ...
<argument> @hfil @ignorespaces @image {cons-1}
@unskip @hfil
@centersub ...enalty @fi @line {@kern @leftskip #1
@kern @rightskip }
@\center ...{@hfil @ignorespaces #1@unskip @hfil }
@let @centersub @relax
l.9527 @center @image{cons-1}
Is that the reason? that epsf.tex is missing?
next prev parent reply other threads:[~2021-03-25 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 17:56 bug#47394: 27.2; admin.el:make-manuals infloops on HTML manuals Eli Zaretskii
2021-03-25 18:31 ` Glenn Morris
2021-03-25 19:17 ` Eli Zaretskii
2021-03-25 19:24 ` Eli Zaretskii
2021-03-25 19:49 ` Glenn Morris
2021-03-25 19:47 ` Glenn Morris
2021-03-25 20:17 ` Eli Zaretskii [this message]
2021-03-25 20:44 ` Eli Zaretskii
2021-03-26 6:31 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ft0jq97x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47394@debbugs.gnu.org \
--cc=rgm@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).