All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0 of 5 v4 for 2014.08] manual-text generation improvements
Date: Sat, 16 Aug 2014 20:08:30 +0200	[thread overview]
Message-ID: <20140816200830.4126dada@free-electrons.com> (raw)
In-Reply-To: <CAHXCMMLMnxoRo4iXBME92kghZ1QDf0EcU7ZyPBUD38OLLkdNaQ@mail.gmail.com>

Dear Samuel Martin,

On Sat, 16 Aug 2014 19:24:42 +0200, Samuel Martin wrote:

> When generating the pdf manual, a2x calls dblatex, which calls xsltproc.
> Here is a verbose log [1].
> During its execution, xsltproc checks for template recursion and
> reaches its limit set to 15000 when processing the target
> package-list.txt file (empirically, this limit allows a 1147-entry
> table).
> To raise this limit, a --maxvars option exists in xsltproc program but
> the latest release of libxslt is buggy and this option is not honored.
> :-(
> Hopefully the fix is already merged upstream [2].
> Backporting this patch is enough to get a working xsltproc, but it
> also means that we now need to build host-libxslt (and a .config) to
> build the manual.
> So, to build the manual we have to run:
> $ make defconfig && make host-libxslt manual
> 
> The main drawback of this fix is that building the manual could now
> require building some host-package.
> 
> This also makes echo to the include statement of the *.mk files
> without having a .config file discussion.
> 
> Anyway, I will prepare a series fixing this, though it is not a
> mandatory for the release
> 
> Note that we have already released a couple of Buildroot versions
> without recieving any complaint about this.

I'm not sure we should enforce building host-libxslt as a dependency of
the manual. Maybe just check the version of xsltproc and bail out with
an error message if it's not the appropriate version. I believe most
people are just using the pre-generated versions of the manual that are
online on Buildroot website. So it's up to us to have the appropriate
xsltproc version there.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-08-16 18:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 13:40 [Buildroot] [PATCH 0 of 5 v4 for 2014.08] manual-text generation improvements Thomas De Schampheleire
2014-08-15 13:40 ` [Buildroot] [PATCH 1 of 5 v4 for 2014.08] Makefile: unconditionally include pkg-utils.mk Thomas De Schampheleire
2014-08-15 22:04   ` Yann E. MORIN
2014-08-15 13:40 ` [Buildroot] [PATCH 2 of 5 v4 for 2014.08] gendoc infra: use $(pkgname) instead of explicitly passing 'manual' Thomas De Schampheleire
2014-08-15 14:50   ` Samuel Martin
2014-08-15 22:13   ` Yann E. MORIN
2014-08-15 13:40 ` [Buildroot] [PATCH 3 of 5 v4 for 2014.08] gendoc infra: add support for asciidoc configuration files Thomas De Schampheleire
2014-08-15 22:23   ` Yann E. MORIN
2014-08-15 13:40 ` [Buildroot] [PATCH 4 of 5 v4 for 2014.08] manual-text: make sure URLs are displayed if a link text was provided Thomas De Schampheleire
2014-08-15 22:32   ` Yann E. MORIN
2014-08-15 13:40 ` [Buildroot] [PATCH 5 of 5 v4 for 2014.08] manual-text: hide image representations Thomas De Schampheleire
2014-08-15 22:45   ` Yann E. MORIN
2014-08-15 14:53 ` [Buildroot] [PATCH 0 of 5 v4 for 2014.08] manual-text generation improvements Samuel Martin
2014-08-16  7:35 ` Thomas Petazzoni
2014-08-16 10:15   ` Thomas De Schampheleire
2014-08-16 11:00     ` Samuel Martin
2014-08-16 17:24       ` Samuel Martin
2014-08-16 18:08         ` Thomas Petazzoni [this message]
2014-08-16 18:35         ` Thomas De Schampheleire
2014-08-16 19:39           ` Samuel Martin
2014-08-17 10:17             ` Thomas De Schampheleire

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=20140816200830.4126dada@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.