This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] fix libxl build issues

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] fix libxl build issues
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Mon, 20 Sep 2010 16:38:17 +0300
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 20 Sep 2010 06:39:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C977EC40200007800017BCD@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4C977EC40200007800017BCD@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Mon, Sep 20, 2010 at 02:33:24PM +0100, Jan Beulich wrote:
> Building in a tree with read-only source files failed because the flex/
> bison generated files are left in place.
> All of the source files (instead of all of the object files) were
> depending on libxl.h (in particular forcing the needless re-generation
> of the flex/bison generated files).
> For _libxl_types.[ch] a single non-pattern rule was used. For non-
> pattern rules with multiple targets, other than for pattern ones, the
> body gets executed once for each target, causing problems when building
> with -j<n>, <n> >= 2. Convert this rule to a pattern one.
> The flex/bison generated headers pointlessly depended on the
> corresponding source files. Use multiple-target pattern rules instead.
> It would also have been nice if the minimal flex/bison versions needed
> to successfully build libxl were documented: neither flex 2.5.31 nor
> bison 2.1 (as found e.g. on SLE10) is sufficient.

There's a note about this on the Xen4.0 wiki page ("release notes"),
but it could be made more clear, stating the actual versions etc.

So what is actually the required version of flex? 

Should this be written also to some file in the xen source tree? 

-- Pasi

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>