Issuing "make pdfdocs" in the kernel source tree fails with gentoo-sources as well as the latest git sources from kernel.org. The documentation can be built with either 'db2pdf' or 'xmlto'. Hence, the following: 1.) xmlto: I have had no success with this. It is installed by app-text/xmlto-0.0.22. 2a.) db2pdf is not installed by app-text/docbook-sgml-utils-0.6.14[+jadetext], but instead there is '/usr/bin/docbook2pdf'. The fix is easy, patch forthcoming, but see (2b). 2b.) docbook2pdf fails compiling pdf for device-drivers.xml, but see patch forthcoming. Reproducible: Always Steps to Reproduce: 1. cd /usr/src/linux 2. make pdfdocs Actual Results: No pdfs are produced. 'db2pdf' is not found, 'xmlto' is used instead, but aborts with an error (separate bug report? more info? don't really want to follow this path...). Expected Results: Produce beautiful pdfs...
Created attachment 201409 [details, diff] Use docbook2pdf instead of db2pdf. This also fixes the "psdocs" target.
Created attachment 201410 [details, diff] Needed to compile device-drivers.pdf. I don't actually know what it does... :-(
Forgot to mention that the last patch solves the following issue: [... many, many warnings ...] ! TeX capacity exceeded, sorry [number of strings=37891]. \IfFileExists #1#2#3->\openin \@inputcheck #1 \ifeof \@inputcheck \ifx \inpu... l.178868 {} \Seq% ! ==> Fatal error occurred, no output PDF file produced! Transcript written on device-drivers.log.
then bug was fixed ? can we mark as fixed?
(In reply to comment #4) > then bug was fixed ? > can we mark as fixed? > It hasn't exactly been fixed yet. Should I file this upstream? I suppose you could close this bug as it isn't exactly mission-critical... :-)
I'll have to mark this as a duplicate of bug #111041. Basically, the kernel is not to blame for the issue and the problem, most probably, lies on the tools being used for the PDF creation. Now, bug #111041 is an ancient bug that NEEDSINFO and is assigned to the Gentoo Text-Markup Team. I'll give it a gentle poke to wake up and I'll let a more suitable team take over. I'll take the initiative and add you to the CC list of bug #111041! Thanks for the bug report, Henry :) *** This bug has been marked as a duplicate of bug 111041 ***