From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Jim Davis <jim.epost@gmail.com>, Jonathan Corbet <corbet@lwn.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC 0/4] Fix PDF build errors
Date: Wed, 02 Nov 2016 13:14:47 +0200 [thread overview]
Message-ID: <87lgx2jfq0.fsf@intel.com> (raw)
In-Reply-To: <cover.1478040090.git.mchehab@osg.samsung.com>
On Wed, 02 Nov 2016, Mauro Carvalho Chehab <mchehab@osg.samsung.com> wrote:
> This series address a series of errors during PDF generation from
> media documentation.
>
> Please notice that patch 2 carries on a PDF conversion from a PNG
> image, because Sphinx is not smart enough to do the convertion.
>
> This is a temporary solution (That's why I'm marking this series
> as RFC).
This seems to work on top of docs-next.
...but it'll break again if we include the missing admin-guide in the
build. :(
BR,
Jani.
>From c296287c65f4b6ad6272171456dcf8508c92ae2f Mon Sep 17 00:00:00 2001
From: Jani Nikula <jani.nikula@intel.com>
Date: Wed, 2 Nov 2016 13:05:59 +0200
Subject: [PATCH] Documentation/sphinx: include admin-guide in the latex/pdf
build
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
Cc: Jani Nikula <jani.nikula@intel.com>
Fix the warning:
WARNING: "latex_documents" config value references unknown document
user/index
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
Sadly, this breaks the pdf build with:
! TeX capacity exceeded, sorry [main memory size=5000000].
\FV@Space ...ionary {\copy \sphinxvisiblespacebox
}{\sphinxafterbreak } {\ke...
l.3711 ...\PYG{n}{be} \PYG{n}{used} \PYG{n+nb}{to}
Output written on linux-user.pdf (15 pages).
Transcript written on linux-user.log.
Makefile:66: recipe for target 'linux-user.pdf' failed
make[2]: *** [linux-user.pdf] Error 1
Documentation/Makefile.sphinx:83: recipe for target 'pdfdocs' failed
make[1]: *** [pdfdocs] Error 2
Makefile:1442: recipe for target 'pdfdocs' failed
make: *** [pdfdocs] Error 2
---
Documentation/conf.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/conf.py b/Documentation/conf.py
index 814c336e5f5e..0c758a4f61f1 100644
--- a/Documentation/conf.py
+++ b/Documentation/conf.py
@@ -340,7 +340,7 @@ if minor > 3:
# (source start file, target name, title,
# author, documentclass [howto, manual, or own class]).
latex_documents = [
- ('user/index', 'linux-user.tex', 'Linux Kernel User Documentation',
+ ('admin-guide/index', 'linux-user.tex', 'Linux Kernel User Documentation',
'The kernel development community', 'manual'),
('kernel-documentation', 'kernel-documentation.tex', 'The Linux Kernel Documentation',
'The kernel development community', 'manual'),
--
2.1.4
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-11-02 11:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 22:44 [PATCH RFC 0/4] Fix PDF build errors Mauro Carvalho Chehab
2016-11-01 22:44 ` [PATCH RFC 1/4] docs-rst: fix " Mauro Carvalho Chehab
2016-11-02 15:03 ` Markus Heiser
2016-11-02 15:06 ` Markus Heiser
2016-11-01 22:44 ` [PATCH RFC 2/4] [media] subdev-formats.rst: we need a pdf picture for bayer Mauro Carvalho Chehab
2016-11-01 22:44 ` [PATCH RFC 3/4] [media] subdev-formats.rst: don't use adjustbox on a longtable Mauro Carvalho Chehab
2016-11-01 22:44 ` [PATCH RFC 4/4] [media] subdev-formats.rst: add missing columns to tabularcolumns Mauro Carvalho Chehab
2016-11-01 22:53 ` [PATCH RFC 0/4] Fix PDF build errors Mauro Carvalho Chehab
2016-11-02 11:14 ` Jani Nikula [this message]
2016-11-02 12:20 ` Mauro Carvalho Chehab
2016-11-02 13:27 ` Jani Nikula
2016-11-02 16:36 ` Mauro Carvalho Chehab
2016-11-02 21:47 ` Fengguang Wu
2016-11-02 16:08 ` Markus Heiser
2016-11-02 16:47 ` Mauro Carvalho Chehab
2016-11-02 17:07 ` Markus Heiser
2016-11-03 9:11 ` Jani Nikula
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=87lgx2jfq0.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=corbet@lwn.net \
--cc=jim.epost@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mchehab@osg.samsung.com \
/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;
as well as URLs for NNTP newsgroup(s).