From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv4] gdb: prevent building the documentation
Date: Thu, 1 Oct 2015 09:41:52 +0100 [thread overview]
Message-ID: <560CF1D0.3090608@imgtec.com> (raw)
In-Reply-To: <20151001091137.4bc06d8a@free-electrons.com>
Hello Thomas, Romain,
On 10/01/2015 08:11 AM, Thomas Petazzoni wrote:
> Vicente, Romain,
>
> 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>
>
> Seems like this is not yet working completely for all situations:
>
> http://autobuild.buildroot.org/results/244/2442e697d8a300496434fd42fcb1ee3941d13e06/build-end.log
I will have a look.
Romain, how is going the upstream request about the --disable-docs option?
Regards,
Vincent.
> Best regards,
>
> Thomas
>
next prev parent reply other threads:[~2015-10-01 8:41 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
2015-10-01 7:11 ` Thomas Petazzoni
2015-10-01 8:41 ` Vicente Olivert Riera [this message]
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=560CF1D0.3090608@imgtec.com \
--to=vincent.riera@imgtec.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.