From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jim Davis <jim.epost@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH 0/5] Make PDF builds work again
Date: Sun, 18 Jun 2017 22:18:29 -0300 [thread overview]
Message-ID: <20170618221829.4573592b@vento.lan> (raw)
In-Reply-To: <20170618234630.19964-1-corbet@lwn.net>
Hi Jon,
Em Sun, 18 Jun 2017 17:46:25 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> I've just spent rather more time than I would like figuring out why the PDF
> builds fail and what was needed to fix it. The result is the following
> patch series. It's a combination of little mistakes and fragility in the
> whole PDF build tool chain.
Yeah, the PDF toolchain is very fragile. Yet, I'm pretty sure I was able
to build PDF in the past without noticing the problems fixed by patches
1 and 2. Maybe the bugs has to do with some specific incompatibility with
toolchain versions.
What Sphinx version are you using?
It is too late now, but tomorrow I'll test with a few Spinx versions
and see if PDF builds equally well with them.
>
> Mauro, Daniel: Do you want the last two? Or otherwise give me acks? I'd
> like to send the set Linusward forthwith so that 4.12 can come out with
> a working PDF build.
For the media and EDAC changes (patches 3 and 4), once I test it,
feel free to add my ack and send via your tree:
Acked-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
>
> In general, I'm dismayed by the fragility of the whole thing. I'm also a
> little concerned that nobody except Jim complained about the problem.
Actually, despite any "errors", usually it produces the PDF files.
I have a robot building just the media documentation, daily basis,
from media development tree, at:
https://linuxtv.org/downloads/v4l-dvb-apis-new/media.pdf
The robot is using Sphinx 1.4.8 version.
> Perhaps nobody really cares about PDF output anymore? In the absence of a
> concerted effort on somebody's part, I predict that PDF building will be
> broken much of the time. I have to wonder if it's worth it...
>
> Jonathan Corbet (5):
> Docs: Include the Latex "ifthen" package
> Docs: Remove redundant geometry package inclusion
> Docs: fix table problems in ras.rst
> Docs: Use kernel-figure in vidioc-g-selection.rst
> DRM: Fix an incorrectly formatted table
>
> Documentation/admin-guide/ras.rst | 10 ++--
> Documentation/conf.py | 3 +-
> .../media/uapi/v4l/vidioc-g-selection.rst | 4 +-
> include/drm/bridge/dw_hdmi.h | 70 +++++++++++-----------
> 4 files changed, 43 insertions(+), 44 deletions(-)
>
Thanks,
Mauro
next prev parent reply other threads:[~2017-06-19 1:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 23:46 [PATCH 0/5] Make PDF builds work again Jonathan Corbet
2017-06-18 23:46 ` [PATCH 1/5] Docs: Include the Latex "ifthen" package Jonathan Corbet
2017-06-18 23:46 ` [PATCH 2/5] Docs: Remove redundant geometry package inclusion Jonathan Corbet
2017-06-19 10:30 ` Mauro Carvalho Chehab
2017-06-19 10:49 ` Mauro Carvalho Chehab
2017-06-23 19:39 ` Jonathan Corbet
2017-06-23 21:26 ` Mauro Carvalho Chehab
2017-06-18 23:46 ` [PATCH 3/5] Docs: fix table problems in ras.rst Jonathan Corbet
2017-06-18 23:46 ` [PATCH 4/5] Docs: Use kernel-figure in vidioc-g-selection.rst Jonathan Corbet
2017-06-18 23:46 ` [PATCH 5/5] DRM: Fix an incorrectly formatted table Jonathan Corbet
2017-06-18 23:48 ` [PATCH 0/5] Make PDF builds work again Jonathan Corbet
2017-06-19 1:18 ` Mauro Carvalho Chehab [this message]
2017-06-19 14:43 ` Mauro Carvalho Chehab
2017-07-03 8:25 ` Daniel Vetter
2017-07-03 12:44 ` Jonathan Corbet
2017-07-05 21:22 ` Jim Davis
2017-07-06 8:28 ` Markus Heiser
2017-07-06 9:54 ` Mauro Carvalho Chehab
2017-07-05 20:03 ` Frank Rowand
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=20170618221829.4573592b@vento.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=jim.epost@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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