From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xenproject.org,
Ed Swierk <eswierk@skyportsystems.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] libxl: Fix building libxlu_cfg_y.y with bison 3.0
Date: Tue, 2 Dec 2014 14:00:55 +0000 [thread overview]
Message-ID: <547DC617.8020107@citrix.com> (raw)
In-Reply-To: <1417528036.24320.32.camel@citrix.com>
On 02/12/14 13:47, Ian Campbell wrote:
> On Mon, 2014-12-01 at 12:19 +0000, Wei Liu wrote:
>> On Mon, Dec 01, 2014 at 09:42:13AM +0000, Ian Campbell wrote:
>>> On Sat, 2014-11-29 at 21:23 -0800, Ed Swierk wrote:
>>>> - Use %lex-param instead of obsolete YYLEX_PARAM to override lex scanner
>>>> parameter
>>>> - Change deprecated %name-prefix= to %name-prefix
>>>>
>>>> Tested against bison 2.4.1 and 3.0.2.
>>>>
>>>> Signed-off-by: Ed Swierk <eswierk@skyportsystems.com>
>>> Copying Ian J who is the bison guy among the toolstack maintainers.
>>>
>> FWIW I can confirm that libxlu_cfg_y.y won't build in Debian Jessie
>> (bison 3.0.2) as is. And this patch fixes the problem for me.
> That would seem like a pretty strong case for 4.5, *except* we ship the
> generated files so it should be possible to build anywhere without
> requiring any version of bison at all. If Bison is installed then
> "./configure BISON=/bin/true" or some such might be needed to stop it
> trying to regenerate.
>
> Konrad, any thoughts.
The automatically generating doesn't actually work. Depending on the
relative timestamps caused by a SCM checkout, or a tarball extraction,
the files will be attempted to be regenerated.
These files are regenerated in the XenServer build, simply because of
their order in the archived tarball.
~Andrew
next prev parent reply other threads:[~2014-12-02 14:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 5:23 [PATCH] libxl: Fix building libxlu_cfg_y.y with bison 3.0 Ed Swierk
2014-12-01 9:42 ` Ian Campbell
2014-12-01 12:19 ` Wei Liu
2014-12-02 13:47 ` Ian Campbell
2014-12-02 14:00 ` Andrew Cooper [this message]
2014-12-02 17:49 ` Ed Swierk
2014-12-03 9:53 ` Ian Campbell
2014-12-03 10:01 ` Olaf Hering
2014-12-09 15:25 ` Ian Jackson
2014-12-10 16:41 ` Konrad Rzeszutek Wilk
2014-12-10 16:44 ` Ian Campbell
2014-12-10 17:02 ` Konrad Rzeszutek Wilk
2015-01-06 15:28 ` Ian Jackson
2014-12-02 18:32 ` Konrad Rzeszutek Wilk
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=547DC617.8020107@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=eswierk@skyportsystems.com \
--cc=konrad.wilk@oracle.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 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.