From mboxrd@z Thu Jan 1 00:00:00 1970 From: Don Slutz Subject: Re: --enable-xsm ? Date: Thu, 15 Jan 2015 11:53:20 -0500 Message-ID: <54B7F080.2030502@terremark.com> References: <20150113192758.GA30253@localhost.localdomain> <54B5838A.5020205@tycho.nsa.gov> <54B63FAD0200007800054A4C@mail.emea.novell.com> <20150114183909.GB2013@l.oracle.com> <1421314845.19103.303.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YBnfh-0005P3-Cd for xen-devel@lists.xenproject.org; Thu, 15 Jan 2015 16:53:25 +0000 In-Reply-To: <1421314845.19103.303.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell , Konrad Rzeszutek Wilk Cc: xen-devel@lists.xenproject.org, Daniel De Graaf , Jan Beulich List-Id: xen-devel@lists.xenproject.org On 01/15/15 04:40, Ian Campbell wrote: > On Wed, 2015-01-14 at 13:39 -0500, Konrad Rzeszutek Wilk wrote: >> On Wed, Jan 14, 2015 at 09:06:37AM +0000, Jan Beulich wrote: >>>>>> On 13.01.15 at 21:43, wrote: >>>> On 01/13/2015 02:27 PM, Konrad Rzeszutek Wilk wrote: >>>>> I was wondering if there would be any plans for configure.ac >>>>> (or the m4 scripts) to have an --enable-xsm which would set >>>>> XSM_ENABLE (or FLASK_ENABLE) to true? >>>>> >>>>> Right now by default to build with XSM one has to manually change >>>>> the Config.mk ENABLE_XSM option to 'y'. This is not strictly true. I see the option as XSM_ENABLE. And docs/misc/xsm-flask.txt correctly states that a .config file can specify this. Also you can add XSM_ENABLE=y to the make command line. And in bash, export XSM_ENABLE=y works. All of these work without a manual change to Config.mk -Don Slutz >>>> Is the hypervisor build allowed to depend on having run ./configure >>>> now? I think this was the reason why config.mk is being used. >>> Correct - configury only controls the tools (and stubdom iirc). >> Ah that is right. Should we expand on that then? Make the hypervisor >> build with different configure options? > The hypervisor maintainers have indicated repeatedly that they do not > want building the hypervisor to require running configure. Which makes > sense, since Xen has no dependency on the userspace environment. > > Ian. > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel