Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] gdb: prevent building the documentation
Date: Wed, 9 Sep 2015 16:29:24 +0100	[thread overview]
Message-ID: <55F05054.5080907@imgtec.com> (raw)
In-Reply-To: <20150909171426.19f79d78@free-electrons.com>

Dear Thomas Petazzoni,

On 09/09/2015 04:14 PM, Thomas Petazzoni wrote:
> Dear Vicente Olivert Riera,
> 
> On Wed, 9 Sep 2015 15:49:07 +0100, Vicente Olivert Riera wrote:
> 
>>> But in any case, if host-texinfo is no longer needed to build the ARC
>>> binutils, then indeed we can drop the host-texinfo dependency, and drop
>>> the host-texinfo package as well.
>>
>> Maybe this is the reason why host-texinfo is no longer needed:
>>
>> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=bba33ab1e0f7d2ebd8f8435f92ed12e2a3c558a4
> 
> Very possible indeed. But that would only fix the problem for release
> tarballs, as the commit log suggests. In binutils, we were depending on
> host-texinfo only for ARC, because for ARC, we are pulling the binutils
> sources from git, not from a release tarball.

well, for ARC we are also downloading a tarball:

https://github.com/foss-for-synopsys-dwc-arc-processors/binutils-gdb/archive/arc-2015.06.tar.gz

But yeah, that tarball doesn't include the fixes introduced by that
commit. However, it includes an interesting comment in
bfs/doc/Makefile.{am,in} (the two files that commit patches):

# We do not depend on chew directly so that we can distribute the info
# files, and permit people to rebuild them, without requiring the makeinfo
# program.  If somebody tries to rebuild info, but none of the .texi files
# have changed, then nothing will be rebuilt.

Regards,

Vincent.

> 
> Best regards,
> 
> Thomas
> 

  reply	other threads:[~2015-09-09 15:29 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 [this message]
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=55F05054.5080907@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox