linux-kernel - Re: make pdfdocs fails on Debian stable

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: <df9183cc-aecb-6b8d-0580-92c2a678d69f@gmail.com>
Date:   Tue, 4 Jan 2022 16:53:15 +0900
From:   Akira Yokosawa <akiyks@...il.com>
To:     Christoph Hellwig <hch@....de>
Cc:     corbet@....net, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org, mchehab@...nel.org
Subject: Re: make pdfdocs fails on Debian stable

On Tue, 4 Jan 2022 08:36:25 +0100, Christoph Hellwig wrote:
> On Tue, Jan 04, 2022 at 04:32:14PM +0900, Akira Yokosawa wrote:
>> I suspect you are suffering from corrupt RCU.aux (or whatever other
>> intermediate files xelatex generates).
>>
>> What happens you run
>>
>>     $ make cleandocs
>>
>> before
>>
>>     $ make SPHINXDIRS=RCU LATEXOPTS="-interaction=interactive" pdfdocs
>>
>> ?
> 
> The last lines of that below:
> 
> LaTeX Warning: Float too large for page by 8477.29312pt on input line 10581.
> 
> 
> LaTeX Warning: Hyper reference `Design/Memory-Ordering/Tree-RCU-Memory-Ordering
> :forcing-quiescent-states' on page 104 undefined on input line 10593.
> 
> 
> LaTeX Warning: Float too large for page by 9533.29312pt on input line 11384.
> 
> 
> LaTeX Warning: Hyper reference `Design/Memory-Ordering/Tree-RCU-Memory-Ordering
> :forcing-quiescent-states' on page 104 undefined on input line 11394.
> 
> [104] [105] [106]
> ! Dimension too large.
> \color@b@x ... #3}\kern \fboxsep }\dimen@ \ht \z@ 
>                                                   \advance \dimen@ \fboxsep ...
> l.12718 \end{sphinxVerbatim}
> 
> ? 
> 

Hmm, I can't reproduce this on docs-next.
On which tree are you building RCU.pdf?

        Thanks, Akira