From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Borislav Petkov <bp@alien8.de>
Cc: perfbook@vger.kernel.org
Subject: Re: perfbook build error
Date: Thu, 11 Dec 2014 09:52:48 -0800 [thread overview]
Message-ID: <20141211175248.GK25340@linux.vnet.ibm.com> (raw)
In-Reply-To: <20141211173210.GE31140@pd.tnic>
On Thu, Dec 11, 2014 at 06:32:10PM +0100, Borislav Petkov wrote:
> Hey Paul,
>
> building perfbook from today here fails with:
>
> Underfull \hbox (badness 7576) in paragraph at lines 1234--1234
> []\T1/ptm/b/n/14.4 Linux-Kernel Equiv-a-lents to
> []
>
> ! Missing { inserted.
> <inserted text>
> {
> l.1246 &
> \co{struct task_struct} \\
> ?
> ! Emergency stop.
> <inserted text>
> {
> l.1246 &
> \co{struct task_struct} \\
> End of file on the terminal!
>
>
> Here is how much of TeX's memory you used:
> 9728 strings out of 495020
> 150662 string characters out of 6181323
> 256123 words of memory out of 5000000
> 12316 multiletter control sequences out of 15000+600000
> 92251 words of font info for 258 fonts, out of 8000000 for 9000
> 14 hyphenation exceptions out of 8191
> 33i,15n,35p,324b,1121s stack positions out of 5000i,500n,10000p,200000b,80000s
> ! ==> Fatal error occurred, no output PDF file produced!
> ---
>
> That's somewhere around that table in toolsoftrade/toolsoftrade.tex,
> lines 1240ff.
>
> Maybe my latex setup is missing something...
Hmmm... Works for me. (Famous last words...)
I am at commit #763eb4b811f9 (Fix resizable-hash figures).
I also sometimes see odd errors like this due to an interrupted run that
leaves bogus .aux files around. A "make clean" will clear this up.
I am also using an oldish version of latex. Let me see what happens
with a more recent version... Well, on that system, it complains about
pstricks.sty not being present. :-/
In the meantime, here is the version of latex I am using:
k$ latex --v
pdfTeX 3.1415926-1.40.10-2.2 (TeX Live 2009/Debian)
kpathsea version 5.0.0
Copyright 2009 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
There is NO warranty. Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
Compiled with libpng 1.2.46; using libpng 1.2.46
Compiled with zlib 1.2.3.4; using zlib 1.2.3.4
Compiled with poppler version 0.18.2
CCing the mailing list in case someone knows how to solve this one.
Thanx, Paul
next parent reply other threads:[~2014-12-11 17:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141211173210.GE31140@pd.tnic>
2014-12-11 17:52 ` Paul E. McKenney [this message]
2014-12-11 19:07 ` perfbook build error Borislav Petkov
2014-12-11 19:17 ` Borislav Petkov
2014-12-11 19:32 ` Paul E. McKenney
2014-12-11 19:59 ` Borislav Petkov
2014-12-11 20:10 ` Paul E. McKenney
2014-12-11 20:22 ` Borislav Petkov
2014-12-11 21:14 ` Paul E. McKenney
2014-12-12 16:38 ` Paul E. McKenney
2014-12-12 17:53 ` Borislav Petkov
[not found] ` <20141212181804.GX25340@linux.vnet.ibm.com>
2014-12-12 18:47 ` Borislav Petkov
2014-12-12 18:58 ` Paul E. McKenney
2014-12-12 19:13 ` Borislav Petkov
2014-12-12 19:30 ` Paul E. McKenney
2014-12-12 20:15 ` Borislav Petkov
2014-12-12 20:27 ` Paul E. McKenney
2014-12-11 19:51 ` Paul E. McKenney
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=20141211175248.GK25340@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=bp@alien8.de \
--cc=perfbook@vger.kernel.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.