From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: fix makeinfo related issue
Date: Fri, 9 Sep 2016 16:43:14 +0200 [thread overview]
Message-ID: <20160909164314.17435856@free-electrons.com> (raw)
In-Reply-To: <c3c573e4-adf3-90e9-cb7c-df3cf0d0ac08@gmail.com>
Hello,
On Thu, 8 Sep 2016 22:45:00 +0200, Romain Naour wrote:
> > -# The .info files in the 2.26 tarball have an incorrect timestamp, so
> > -# binutils tries to re-generate them. In order to avoid the dependency
> > -# on host-texinfo, we simply update the timestamps.
> > -ifeq ($(BR2_BINUTILS_VERSION_2_26_X),y)
> > +# The .info files in the >= 2.26 tarball have an incorrect timestamp,
> > +# so binutils tries to re-generate them. In order to avoid the
> > +# dependency on host-texinfo, we simply update the timestamps.
> > +ifeq ($(BR2_BINUTILS_VERSION_2_26_X)$(BR2_BINUTILS_VERSION_2_27_X),y)
>
> Binutils 2.28 will likely have the same issue, why not inverse the condition ?
> ifneq ($(BR2_BINUTILS_VERSION_2_24_X)$(BR2_BINUTILS_VERSION_2_25_X),)
Right, but maybe I could dream that someone will report the bug to the
binutils maintainers, and that the problem will be fixed in binutils
2.28 ? :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-09 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 19:49 [Buildroot] [PATCH] binutils: fix makeinfo related issue Thomas Petazzoni
2016-09-08 20:45 ` Romain Naour
2016-09-09 14:43 ` Thomas Petazzoni [this message]
2016-09-11 20:50 ` Thomas Petazzoni
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=20160909164314.17435856@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox