From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] package/gdb: host-texinfo needed for full gdb
Date: Wed, 9 Sep 2015 11:51:24 +0200 [thread overview]
Message-ID: <20150909115124.28919804@free-electrons.com> (raw)
In-Reply-To: <55EF582F.1090407@mind.be>
Hello,
On Tue, 8 Sep 2015 23:50:39 +0200, Arnout Vandecappelle wrote:
> Romain patches gdb to avoid recursing in the doc directory [1][2]
> Vicente does the same but with a sed instead of patch [3].
> Brendan adds host-texinfo to dependencies (this patch) [4].
>
> Which one do we choose?
>
> host-texinfo takes a bit of time to build because it also depends on
> host-ncurses, but it's not a huge problem.
>
> The best solution is adding an upstreamable --disable-doc, but that will take a
> bit of work still (esp. because we can't easily autoreconfigure).
>
> So for me Brendan's patch is fine. What do the others think?
On my side, I think I'd prefer for now a $(SED) to remove the doc
directory from the SUBDIRS, in Makefile.in (avoids autoreconf, avoids
per-gdb version patches). And then, Romain has contributed to gdb a
patch to disable the documentation, but as you said, it will take a
while before this patch 1/ gets accepted and 2/ is used in all gdb
versions packaged in Buildroot.
I think I would actually prefer to also do the same trick for all
packages that need host-texinfo, and remove the host-texinfo package.
The host-texinfo package (as is documented in texinfo.mk) was
originally added only because Crosstool-NG needed it as a dependency,
back when we had a Crosstool-NG backend. Now that this backend is done,
I'm not sure it make a lot of sense to build a tool to build
documentation, which nobody will ever use/read.
So I would favor Vicente's patch in fact. Yes, it is not nice to $(SED)
stuff, but it is a whole lot better than building host-texinfo,
host-ncurses, and some totally unused documentation.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-09 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 19:27 [Buildroot] [PATCH v3 1/1] package/gdb: host-texinfo needed for full gdb Brendan Heading
2015-09-08 21:50 ` Arnout Vandecappelle
2015-09-08 22:02 ` Brendan Heading
2015-09-08 22:09 ` Romain Naour
2015-09-08 22:29 ` Arnout Vandecappelle
2015-09-09 9:04 ` Vicente Olivert Riera
2015-09-09 9:51 ` Thomas Petazzoni [this message]
2015-09-09 9:18 ` Vicente Olivert Riera
2015-09-11 17:34 ` Thomas Petazzoni
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=20150909115124.28919804@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.