From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Don Slutz <dslutz@verizon.com>
Cc: xen-devel@lists.xenproject.org,
Daniel De Graaf <dgdegra@tycho.nsa.gov>,
Ian Campbell <Ian.Campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: --enable-xsm ?
Date: Thu, 15 Jan 2015 13:20:13 -0500 [thread overview]
Message-ID: <20150115182012.GG31562@konrad-lan.dumpdata.com> (raw)
In-Reply-To: <54B7F080.2030502@terremark.com>
On Thu, Jan 15, 2015 at 11:53:20AM -0500, Don Slutz wrote:
> 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, <dgdegra@tycho.nsa.gov> 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
That is right. I totally forgot about that :-) Will use that to make
sure I build with XSM enabled. Thanks!
prev parent reply other threads:[~2015-01-15 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 19:27 --enable-xsm ? Konrad Rzeszutek Wilk
2015-01-13 20:43 ` Daniel De Graaf
2015-01-14 9:06 ` Jan Beulich
2015-01-14 18:39 ` Konrad Rzeszutek Wilk
2015-01-15 8:08 ` Jan Beulich
2015-01-15 9:40 ` Ian Campbell
2015-01-15 16:53 ` Don Slutz
2015-01-15 18:20 ` Konrad Rzeszutek Wilk [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=20150115182012.GG31562@konrad-lan.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=dslutz@verizon.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.