From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>,
"Masaki Kanno" <kanno.masaki@jp.fujitsu.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: Build error occurred / python and flex version requirements for Xen 4.0
Date: Tue, 06 Apr 2010 20:30:38 +0100 [thread overview]
Message-ID: <C7E14A6E.FABF%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20100406190757.GJ1878@reaktio.net>
On 06/04/2010 20:07, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:
> I'm in the process of writing a wiki page for Xen 4.0 release,
> and I was thinking of adding a note about this.
>
> A question: in what cases does one need to re-generate the stuff,
> and thus have newer flex than in RHEL5/CentOS5?
Only if you modify the source-tree inputs to flex. If only building the tree
you do not need flex.
-- Keir
prev parent reply other threads:[~2010-04-06 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 0:53 Build error occurred Masaki Kanno
2010-03-04 6:23 ` Keir Fraser
2010-03-04 11:25 ` Ian Jackson
2010-03-04 12:21 ` Masaki Kanno
2010-04-06 19:07 ` Build error occurred / python and flex version requirements for Xen 4.0 Pasi Kärkkäinen
2010-04-06 19:30 ` Keir Fraser [this message]
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=C7E14A6E.FABF%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=kanno.masaki@jp.fujitsu.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).