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 16:45:26 +0200 [thread overview]
Message-ID: <20150909164526.4467be61@free-electrons.com> (raw)
In-Reply-To: <55F044FC.6040608@imgtec.com>
Vicente,
On Wed, 9 Sep 2015 15:41:00 +0100, Vicente Olivert Riera wrote:
> according to the binutils.mk file, only the one for ARC architecture
> needs host-texinfo:
>
> ifeq ($(BR2_arc),y)
> BINUTILS_SITE = $(call
> github,foss-for-synopsys-dwc-arc-processors,binutils-gdb,$(BINUTILS_VERSION))
> BINUTILS_SOURCE = binutils-$(BINUTILS_VERSION).tar.gz
> BINUTILS_FROM_GIT = y
> endif
>
> [snip]
>
> ifeq ($(BINUTILS_FROM_GIT),y)
> BINUTILS_DEPENDENCIES += host-texinfo host-flex host-bison
> HOST_BINUTILS_DEPENDENCIES += host-texinfo host-flex host-bison
> endif
>
> However, I have removed the texinfo package and also removed the
> host-texinfo dependencies from binutils.mk, and it worked fine:
>
> $ grep "BR2_arc=y" .config
> BR2_arc=y
>
> $ ls package/texinfo
> ls: cannot access package/texinfo: No such file or directory
>
> $ ls output/build/host-binutils-arc-2015.06/.stamp_host_installed
> output/build/host-binutils-arc-2015.06/.stamp_host_installed
>
> $ ls output/build/binutils-arc-2015.06/.stamp_target_installed
> output/build/binutils-arc-2015.06/.stamp_target_installed
>
> So this dependency is unnecessary.
Actually, it is not clear to me when binutils/gdb want to rebuild their
documentation. Some versions of gdb did not try to rebuild their
documentation, some did. I wonder if gdb/binutils don't come with a
pre-generated version of the documentation, which might get
re-generated if the timestamps of the generated doc is older than the
documentation source. This is pure guess.
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.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-09 14:45 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 [this message]
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=20150909164526.4467be61@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.