linux-kernel - Re: [PATCH] [KERNEL-DOC] fix tex error when building pdfdocs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070412164851.0c5d6e54.randy.dunlap@oracle.com>
Date:	Thu, 12 Apr 2007 16:48:51 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Borislav Petkov <bbpetkov@...oo.de>
Cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] [KERNEL-DOC] fix tex error when building pdfdocs

On Thu, 12 Apr 2007 22:38:42 +0200 Borislav Petkov wrote:

> When building pdfdocs, the db2pdf converter bails out because of an
> latex-reserved token  - '#' - in the intermediary .tex file which ends up in a
> conversion error with the following error message: 
> 
> <log>
> [15.0.32])
> ! Incomplete \iffalse; all text was ignored after line 8154.
> <inserted text>
>                 \fi
> <*> kernel-hacking.tex
> </log>
> 
> This is a rather arbitrary fix, so suggest away.

Hi,

I don't have a problem with the change, but I don't get that tex error either.
Here is an extract from the .tex file:


{\def\Element%
{451}\def\ProcessingMode%
{title-sosofo-mode}}\#if\endNode{}\endSeq{}\endLink{}\Seq%
{}\Leader%
{}.\endLeader{}\Link%


> Signed-off-by: Borislav Petkov <bbpetkov@...oo.de>
> 
> Index: 21-rc6/Documentation/DocBook/kernel-hacking.tmpl
> ===================================================================
> --- 21-rc6.orig/Documentation/DocBook/kernel-hacking.tmpl
> +++ 21-rc6/Documentation/DocBook/kernel-hacking.tmpl
> @@ -1138,7 +1138,7 @@ static struct block_device_operations op
>    </sect1>
>  
>    <sect1 id="conventions-ifdef">
> -   <title>&num;if</title>
> +   <title>Prepocessor Conditionals</title>
>     
>     <para>
>      It is generally considered cleaner to use macros in header files
> 
> -

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/