From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] package/gdb: host-texinfo needed for full gdb
Date: Wed, 9 Sep 2015 10:04:03 +0100 [thread overview]
Message-ID: <55EFF603.8020203@imgtec.com> (raw)
In-Reply-To: <55EF6133.8060309@mind.be>
Dear all,
On 09/08/2015 11:29 PM, Arnout Vandecappelle wrote:
> On 09-09-15 00:09, Romain Naour wrote:
>> Hi Arnout, All,
>>
>> Le 08/09/2015 23:50, Arnout Vandecappelle a ?crit :
>>> On 08-09-15 21:27, Brendan Heading wrote:
>>>> Fixes :
>>>> http://autobuild.buildroot.net/results/dd5/dd50ed99abb2c8495def826866b184030953f90e/
>>>
>>> So, we now have three versions to fix this:
>>>
>>> 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).
>>
>> I sent a patch to gdb mailing list to add --disable-docs option but it's not
>> tested since I can't regenerate the configure script locally.
>>
>> See https://sourceware.org/ml/gdb-patches/2015-09/msg00073.html
>>
>> I'm waiting for a review.
>>
>>>
>>> So for me Brendan's patch is fine. What do the others think?
>>
>> I would prefer to avoid host-texinfo dependency if possible.
>
> I agree, but perhaps we can commit Brendan's patch until the --disable-docs
> option is there.
Brendan's patch while we wait for --disable-docs sounds as the best
option for me as well.
Regards,
Vincent.
> Regards,
> Arnout
>
>
> [snip[
>
>
next prev parent reply other threads:[~2015-09-09 9:04 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 [this message]
2015-09-09 9:51 ` Thomas Petazzoni
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=55EFF603.8020203@imgtec.com \
--to=vincent.riera@imgtec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox