From: Chong Lu <Chong.Lu@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] bison: update to 3.0.2
Date: Tue, 25 Nov 2014 17:27:10 +0800 [thread overview]
Message-ID: <54744B6E.5040607@windriver.com> (raw)
In-Reply-To: <CAJTo0LYaXhKUPNm8U6o9LJ+kP863M9Q548sjoyQTkMoz0hSyYg@mail.gmail.com>
On 11/24/2014 07:26 PM, Burton, Ross wrote:
>
> On 24 November 2014 at 05:19, Chong Lu <Chong.Lu@windriver.com
> <mailto:Chong.Lu@windriver.com>> wrote:
>
> After I upgrade bison, I test world on qemuppc and qemux86, that's ok.
> Can you tell me, which arch will build failure or how to reproduce
> this failure?
> I will try to fix it.
>
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/104/steps/BuildImages/logs/stdio
>
> That's PPC with poky-lsb. It may be unrelated but the failures
> involve bison. I see that glibc doesn't depend on bison-native so if
> it is running the tool at build time there could be problems with
> bison being replaced during a build.
>
> Ross
Hi Ross,
I try to reproduce this issue in my environment. But I can't get build
failure about glibc.
glibc depends on bison-native:
"glibc" -> "kconfig-frontends-native" -> "bison-native"
I checked glibc source code. In intl/plural.c file, The bison version is
defined:
#define YYBISON_VERSION "2.7"
Does this issue related with sstate?
I build world on some arch, no build failure appear.:-)
Best Regards
Chong
next prev parent reply other threads:[~2014-11-25 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 7:22 [PATCH 0/3] bison: update to 3.0.2 Chong Lu
2014-11-18 7:22 ` [PATCH 1/3] " Chong Lu
2014-11-20 11:20 ` Burton, Ross
2014-11-24 5:19 ` Chong Lu
2014-11-24 11:26 ` Burton, Ross
2014-11-25 9:27 ` Chong Lu [this message]
2014-11-18 7:22 ` [PATCH 2/3] gstreamer: change priv_gst_parse_yylex arguments Chong Lu
2014-11-18 7:22 ` [PATCH 3/3] webkit-gtk: ANGLE doesn't build with bison 3 Chong Lu
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=54744B6E.5040607@windriver.com \
--to=chong.lu@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.