All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gdb: prevent building the documentation
Date: Tue, 8 Sep 2015 15:39:59 +0200	[thread overview]
Message-ID: <55EEE52F.4020904@mind.be> (raw)
In-Reply-To: <1441718565-24492-1-git-send-email-Vincent.Riera@imgtec.com>

On 08-09-15 15:22, Vicente Olivert Riera wrote:
> gdb needs makeinfo to build the documentation. Since we do not provide a
> host-makeinfo package this will fail in any system where makeinfo is
> missing. However, we can workaround this problem by preventing gdb to
> build the documentation.
> 
> Fixes:
> 
>   http://autobuild.buildroot.net/results/dd5/dd50ed99abb2c8495def826866b184030953f90e/
> 
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
>  package/gdb/gdb.mk |    6 ++++++
>  1 files changed, 6 insertions(+), 0 deletions(-)
> 
> diff --git a/package/gdb/gdb.mk b/package/gdb/gdb.mk
> index 338de20..7a8f8c7 100644
> --- a/package/gdb/gdb.mk
> +++ b/package/gdb/gdb.mk
> @@ -114,6 +114,12 @@ else
>  GDB_CONF_OPTS += --without-zlib
>  endif
>  
> +# Prevent gdb to build the documentation
> +define GDB_DISABLE_DOC
> +$(SED) '/^SUBDIRS =/ s/doc//' $(@D)/gdb/Makefile.in
> +endef
> +GDB_PRE_CONFIGURE_HOOKS += GDB_DISABLE_DOC

 Since it is patching the source, it should be POST_PATCH_HOOKS rather than
PRE_CONFIGURE_HOOKS.

 That does mean that people using OVERRIDE_SRCDIR should do this fix in the
overridden source, but I think that's OK.

 Regards,
 Arnout

> +
>  # This removes some unneeded Python scripts and XML target description
>  # files that are not useful for a normal usage of the debugger.
>  define GDB_REMOVE_UNNEEDED_FILES
> 


-- 
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

  reply	other threads:[~2015-09-08 13:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 13:22 [Buildroot] [PATCH] gdb: prevent building the documentation Vicente Olivert Riera
2015-09-08 13:39 ` Arnout Vandecappelle [this message]
2015-09-08 13:49   ` Brendan Heading
2015-09-08 13:53     ` Brendan Heading
2015-09-08 13:55       ` Vicente Olivert Riera
2015-09-09 10:48 ` Arnout Vandecappelle
2015-09-09 10:51   ` Vicente Olivert Riera
2015-09-09 10:53     ` Brendan Heading

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=55EEE52F.4020904@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 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.