All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Heiser <markus.heiser@darmarit.de>
To: Jim Davis <jim.epost@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc List <linux-doc@vger.kernel.org>,
	linux-kernel List <linux-kernel@vger.kernel.org>,
	Jani Nikula <jani.nikula@intel.com>
Subject: Re: make pdfdocs fails with v4.9-rc3
Date: Wed, 2 Nov 2016 15:42:17 +0100	[thread overview]
Message-ID: <45104DBA-5B56-48EA-9E1A-7F088BD8385A@darmarit.de> (raw)
In-Reply-To: <CA+r1ZhiY+sS457TYKNqaF5KKkKFgTJi9u0Y7_qJd10OprjNkiQ@mail.gmail.com>


Am 01.11.2016 um 23:11 schrieb Jim Davis <jim.epost@gmail.com>:

> On Mon, Oct 31, 2016 at 3:41 PM, Mauro Carvalho Chehab
> <mchehab@infradead.org> wrote:
>> Em Mon, 31 Oct 2016 16:40:02 -0600
>> Mauro Carvalho Chehab <mchehab@infradead.org> escreveu:
>> 
>>> Em Mon, 31 Oct 2016 15:04:42 -0700
>>> Jim Davis <jim.epost@gmail.com> escreveu:
> 
> I've no idea where's it's going astray, though there are a number of errors:
> 
> jim@krebstar:~$ grep '^!' /tmp/make-pdfdocs.txt | sort -u
> ! Argument of \LT@max@sel has an extra }.
> ! Extra alignment tab has been changed to \cr.
> ! Extra \endcsname.
> ! Extra \endgroup.
> ! Illegal unit of measure (pt inserted).
> ! Improper alphabetic constant.
> ! LaTeX Error: \begin{document} ended by \end{adjustbox}.
> ! LaTeX Error: \begin{document} ended by \end{longtable}.
> ! LaTeX Error: Something's wrong--perhaps a missing \item.
> ! LaTeX Error: There's no line here to end.
> ! Misplaced \noalign.
> ! Missing \endcsname inserted.
> ! Missing \endgroup inserted.
> ! Missing { inserted.
> ! Missing } inserted.
> ! Missing # inserted in alignment preamble.
> ! Missing number, treated as zero.
> ! Paragraph ended before \LT@entry was complete.
> ! Paragraph ended before \LT@max@sel was complete.
> ! Paragraph ended before \multicolumn was complete.
> ! Undefined control sequence.
> ! You can't use `\hrule' here except wi
> 

FYI: as far as I know those "!LaTeX Error" messages cause TeX 
to end with an error code which stops the make build. 

Since we are not in an interactive mode, xelatex continues
after each "!LaTeX Error" messages and builds the pdf to
its end (even if the content might be broken).. and then,
it ends with exit status !=0.

In those cases (make build stops), we have to study the log file. 

BTW: I prefer Jani's solution, using the "batchmode" [1] and
if a pdf build fails, I have to read the *.log file in the 
latex output folder searching for those "!LaTeX Error". 

[1] https://www.mail-archive.com/linux-doc@vger.kernel.org/msg07462.html

--Markus--

      parent reply	other threads:[~2016-11-02 14:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 18:51 make pdfdocs fails with v4.9-rc3 Jim Davis
2016-10-31 19:15 ` Jonathan Corbet
2016-10-31 20:17   ` Mauro Carvalho Chehab
2016-10-31 20:58     ` Mauro Carvalho Chehab
2016-10-31 22:04       ` Jim Davis
2016-10-31 22:40         ` Mauro Carvalho Chehab
2016-10-31 22:41           ` Mauro Carvalho Chehab
2016-11-01  4:51             ` Mauro Carvalho Chehab
2016-11-01 22:11             ` Jim Davis
2016-11-01 22:49               ` Mauro Carvalho Chehab
2016-11-02 14:42               ` Markus Heiser [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45104DBA-5B56-48EA-9E1A-7F088BD8385A@darmarit.de \
    --to=markus.heiser@darmarit.de \
    --cc=corbet@lwn.net \
    --cc=jani.nikula@intel.com \
    --cc=jim.epost@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.