From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] package/gdb: host-texinfo needed for full gdb
Date: Wed, 9 Sep 2015 00:09:01 +0200 [thread overview]
Message-ID: <55EF5C7D.3040908@openwide.fr> (raw)
In-Reply-To: <55EF582F.1090407@mind.be>
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.
Best regards,
Romain
>
>
> Regards,
> Arnout
>
>
> [1] http://patchwork.ozlabs.org/patch/514907/
> [2] http://patchwork.ozlabs.org/patch/514908/
> [3] http://patchwork.ozlabs.org/patch/515401/
> [4] http://patchwork.ozlabs.org/patch/515527/
>
>>
>> .. and many others.
>>
>> when building the full gdb (ie not just gdbserver) on the host or target
>> the "make install" phase seems to expect makeinfo (from texinfo) to be
>> present.
>>
>> Added a dependency so that the host always depends on host-texinfo, and
>> the target depends on it if the full GDB is being built. No need to set
>> ac_cv_prog_MAKEINFO anymore as it doesn't seem to achieve the desired
>> effect.
>>
>> Signed-off-by: Brendan Heading <brendanheading@gmail.com>
> [snip]
>
>
next prev parent reply other threads:[~2015-09-08 22:09 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 [this message]
2015-09-08 22:29 ` Arnout Vandecappelle
2015-09-09 9:04 ` Vicente Olivert Riera
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=55EF5C7D.3040908@openwide.fr \
--to=romain.naour@openwide.fr \
--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