From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv4] gdb: prevent building the documentation
Date: Fri, 11 Sep 2015 19:32:10 +0200 [thread overview]
Message-ID: <20150911193210.798bebce@free-electrons.com> (raw)
In-Reply-To: <1441875400-16473-1-git-send-email-Vincent.Riera@imgtec.com>
Dear Vicente Olivert Riera,
On Thu, 10 Sep 2015 09:56:40 +0100, Vicente Olivert Riera wrote:
> Force gdb to not build the documentation. This way we avoid depending on
> host-texinfo. This is a temporary fix until upstream accepts a proposed
> --disable-docs configure option.
>
> Since the documentation will not be build at all, we can remove the
> parts related to host-texinfo and MAKEINFO in the gdb.mk file.
>
> Fixes:
>
> http://autobuild.buildroot.net/results/dd5/dd50ed99abb2c8495def826866b184030953f90e/
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Tested-by: Brendan Heading <brendanheading@gmail.com>
> ---
> Changes v3 -> v4:
> - Use a pre-configure-hook instead of post-patch-hook as the last one
> is not called in the OVERRIDE_SRCDIR case (Arnout Vandecappelle)
> Changes v2 -> v3:
> - Use the post-patch-hook also for host-gdb (Brendan Heading)
> - Remove unnecessary GDB_FROM_GIT (Romain Naour)
> Changes v1 -> v2:
> - Indent the sed command
> - Use a post-patch-hook instead of pre-configure-hook
> - Remove the parts related to host-texinfo and MAKEINFO
> - Ammend the commit log to be more appropriate
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-11 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 8:56 [Buildroot] [PATCHv4] gdb: prevent building the documentation Vicente Olivert Riera
2015-09-10 13:23 ` Arnout Vandecappelle
2015-09-11 17:32 ` Thomas Petazzoni [this message]
2015-10-01 7:11 ` Thomas Petazzoni
2015-10-01 8:41 ` Vicente Olivert Riera
2015-10-02 22:18 ` Romain Naour
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=20150911193210.798bebce@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.