From: Phil Blundell <pb@pbcl.net>
To: Yuanjie Huang <Yuanjie.Huang@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] glibc: Fix timestamp of plural.c after unpack
Date: Tue, 11 Oct 2016 12:53:59 +0100 [thread overview]
Message-ID: <1476186839.16008.43.camel@pbcl.net> (raw)
In-Reply-To: <20161011080241.24267-1-Yuanjie.Huang@windriver.com>
On Tue, 2016-10-11 at 16:02 +0800, Yuanjie Huang wrote:
> From: Yuanjie Huang <yuanjie.huang@windriver.com>
>
> Source file plural.c might be updated with bison from plural.y, touch
> it
> before applying patches so that this file is consistent across
> builds.
I think it would be better to just configure glibc explicitly without
bison (BISON=no). It doesn't DEPEND on bison-native anyway so it ought
never to be using it.
p.
next prev parent reply other threads:[~2016-10-11 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 8:02 [PATCH] glibc: Fix timestamp of plural.c after unpack Yuanjie Huang
2016-10-11 8:37 ` Mark Hatle
2016-10-11 9:17 ` Burton, Ross
2016-10-11 9:50 ` Yuanjie Huang
2016-10-11 10:29 ` Mark Hatle
2016-10-11 9:22 ` Enrico Scholz
2016-10-11 9:46 ` Gary Thomas
2016-10-11 10:31 ` Mark Hatle
2016-10-11 11:53 ` Phil Blundell [this message]
2016-10-11 12:56 ` Mark Hatle
2016-10-11 13:01 ` Phil Blundell
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=1476186839.16008.43.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=Yuanjie.Huang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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