From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu Date: Mon, 11 Aug 2008 13:06:06 +0200 Message-ID: <48A01D1E.3070502@redhat.com> References: <489B33A2.50306@eu.citrix.com> <18592.3938.942391.705513@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <18592.3938.942391.705513@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: xen-devel@lists.xensource.com, Keir Fraser , Samuel Thibault , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org Ian Jackson wrote: > Keir Fraser writes ("Re: [Xen-devel] Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu"): >> It goes without saying that this shouldn't be the default when building out >> of the Xen repository using our build system. Not everyone wants to install >> our headers on the build machine. But making /usr/include the default and >> having Xen's build system override at configure time would be fine. > > I agree that having this as a build option is a good idea. > > I think it would be better not to have it be the default, though. It should be the default for the git tree, so it can be checked out and built as-is without having to pull more stuff. The xen build system can easily override it when it builds qemu-dm as part of a complete xen build. > Autobuilder systems typically want to avoid accidentally picking up > stuff from the build system environment, so that builds stay > reproducible. ... or they prepare the environment the way they want it. cheers, Gerd -- http://kraxel.fedorapeople.org/xenner/