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 12:10:14 -0800 [thread overview]
Message-ID: <20141211201014.GN25340@linux.vnet.ibm.com> (raw)
In-Reply-To: <20141211195922.GH31140@pd.tnic>
On Thu, Dec 11, 2014 at 08:59:22PM +0100, Borislav Petkov wrote:
> On Thu, Dec 11, 2014 at 11:32:30AM -0800, Paul E. McKenney wrote:
> > Or the newer version of latex doesn't like the \co{} macro definition.
> >
> > One hack-around is to replace the definition on line 38 of perfbook.tex
> > with something like this:
> >
> > \newcommand{\co}[1]{\url{#1}}
> >
> > Does that help, modulo the resulting bogus links?
>
> Nah, this chokes on the '#' char:
>
> ! Illegal parameter number in definition of \Hy@tempa.
> <to be read again>
> d
> l.876 two \co{#define}
> statements, giving us not one but two ways to create
> ?
> ! Emergency stop.
> <to be read again>
> d
> l.876 two \co{#define}
> statements, giving us not one but two ways to create
> End of file on the terminal!
> ---
That is odd given that URLs really can contain "#"...
> Btw, don't waste too much time with it before you can reproduce it
> yourself and can actually confirm it is a latex issue. I might be
> missing packages or so... although updating texlive-latex-* works out
> fine and pulls in whatever it needs.
>
> Btw, it looks like it has trouble with this custom defined command. Built-in
> stuff works:
>
> ---
> diff --git a/toolsoftrade/toolsoftrade.tex b/toolsoftrade/toolsoftrade.tex
> index c98f3a78652f..e227fe7363fb 100644
> --- a/toolsoftrade/toolsoftrade.tex
> +++ b/toolsoftrade/toolsoftrade.tex
> @@ -1242,7 +1242,7 @@ but may be implemented straightforwardly as follows:
> \hline
> \hline
> Thread Management
> - & \co{pthread_t}
> + & \L test
I am guessing that \L chokes on underscores, otherwise, it would be an
attractive alternative to \co{}. (It does choke on underscores in my
old environment.)
> & \co{struct task_struct} \\
> \cline{2-3}
> & \co{pthread_create()}
> --
>
> I need to investigate more.
Please let me know how it goes!
Thanx, Paul
next prev parent reply other threads:[~2014-12-11 20:10 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 ` perfbook build error Paul E. McKenney
2014-12-11 19:07 ` 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 [this message]
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=20141211201014.GN25340@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox