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: Mon, 24 Nov 2014 13:19:58 +0800 [thread overview]
Message-ID: <5472BFFE.4090600@windriver.com> (raw)
In-Reply-To: <CAJTo0Lb48t-x82qYKAmOY5TmvbWmNvSHV2tSkT+JqyLXcDjxtw@mail.gmail.com>
On 11/20/2014 07:20 PM, Burton, Ross wrote:
>
> On 18 November 2014 07:22, Chong Lu <Chong.Lu@windriver.com
> <mailto:Chong.Lu@windriver.com>> wrote:
>
> Upgrade bison to 3.0.2.
>
>
> In testing glibc fails to build on some arches and this patch may be
> the cause:
>
> | plural.c: In function '__gettextparse':
> | plural.c:64:25: error: too few arguments to function '__gettextlex'
> | #define yylex __gettextlex
> | ^
> | plural.c:1296:16: note: in expansion of macro 'yylex'
> | yychar = yylex (&yylval);
> | ^
> | plural.c:64:25: note: declared here
> | #define yylex __gettextlex
> | ^
> | plural.y:69:12: note: in expansion of macro 'yylex'
> | static int yylex PARAMS ((YYSTYPE *lval, const char **pexp));
> | ^
> | plural.y:178:29: error: 'arg' undeclared (first use in this function)
> | ((struct parse_args *) arg)->res = $1;
>
> Does that look like something that bison 3 broke? If so we need to
> fix glibc.
>
> Ross
Hi Ross,
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.
Best Regards
Chong
next prev parent reply other threads:[~2014-11-24 5:20 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 [this message]
2014-11-24 11:26 ` Burton, Ross
2014-11-25 9:27 ` Chong Lu
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=5472BFFE.4090600@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.