All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] gdb: prevent building the documentation
Date: Wed, 9 Sep 2015 15:49:13 +0200	[thread overview]
Message-ID: <20150909154913.72954fbc@free-electrons.com> (raw)
In-Reply-To: <1441800739-14854-1-git-send-email-Vincent.Riera@imgtec.com>

Dear Vicente Olivert Riera,

On Wed, 9 Sep 2015 13:12:19 +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>

Maybe we could do a similar thing for the binutils package (which is
the only other user of the host-texinfo package), and then remove the
host-texinfo package altogether. That's obviously a completely separate
set of changes.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2015-09-09 13:49 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 [this message]
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

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=20150909154913.72954fbc@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.