From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] gdb: prevent building the documentation
Date: Wed, 9 Sep 2015 21:04:35 +0200 [thread overview]
Message-ID: <55F082C3.1030605@mind.be> (raw)
In-Reply-To: <1441800739-14854-1-git-send-email-Vincent.Riera@imgtec.com>
On 09-09-15 14:12, 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>
[snip]
> +# Prevent gdb to build the documentation
> +define GDB_DISABLE_DOC
> + $(SED) '/^SUBDIRS =/ s/doc//' $(@D)/gdb/Makefile.in
> +endef
> +GDB_POST_PATCH_HOOKS += GDB_DISABLE_DOC
> +HOST_GDB_POST_PATCH_HOOKS += GDB_DISABLE_DOC
Sorry to be fickle, but post-patch hooks are not called in the OVERRIDE_SRCDIR
case, so perhaps it's better after all to do it in pre-configure (with
appropriate comment why).
Or perhaps we should call post-patch hooks in .stamp-rsynced...
Regards,
Arnout
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2015-09-09 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 12:12 [Buildroot] [PATCHv3] gdb: prevent building the documentation Vicente Olivert Riera
2015-09-09 12:42 ` Brendan Heading
2015-09-09 13:49 ` Thomas Petazzoni
2015-09-09 13:58 ` Brendan Heading
2015-09-09 14:29 ` Thomas Petazzoni
2015-09-09 14:41 ` Vicente Olivert Riera
2015-09-09 14:45 ` Thomas Petazzoni
2015-09-09 14:49 ` Vicente Olivert Riera
2015-09-09 15:14 ` Thomas Petazzoni
2015-09-09 15:29 ` Vicente Olivert Riera
2015-09-09 19:04 ` Arnout Vandecappelle [this message]
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=55F082C3.1030605@mind.be \
--to=arnout@mind.be \
--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