From: Tim Deegan <tim@xen.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Christoph Egger <chegger@amazon.de>, Keir Fraser <keir@xen.org>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] Make sure to use tools as found by configure
Date: Fri, 10 May 2013 13:49:17 +0100 [thread overview]
Message-ID: <20130510124917.GA87221@ocelot.phlegethon.org> (raw)
In-Reply-To: <1368188087.27857.101.camel@zakaz.uk.xensource.com>
At 13:14 +0100 on 10 May (1368191687), Ian Campbell wrote:
> On Fri, 2013-05-10 at 12:59 +0100, Christoph Egger wrote:
> > Hi,
> >
> > attached patch makes the build process work as described at
> > http://wiki.xen.org/wiki/Compiling_Xen_From_Source_on_NetBSD
> >
> > Without this patch compiling the xen kernel fails with
> > python: No such file or directory
>
> >
> > Note, this patch enforces to run configure before you
> > can compile the xen kernel.
>
> > This is already required to build tools and stubdom anyway.
>
> The hypervisor maintainers have explicitly required that configure not
> be required to build the hypervisor. You can be pretty sure they will
> NAK this change, which you didn't even CC to them, I have added them
> now.
Indeed, on that basis: Nack. Please confine autoconf-related goop to
the parts of the tree that use it.
Tim.
next prev parent reply other threads:[~2013-05-10 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 11:59 [PATCH] Make sure to use tools as found by configure Christoph Egger
2013-05-10 12:14 ` Ian Campbell
2013-05-10 12:49 ` Tim Deegan [this message]
2013-05-10 17:06 ` Matt Wilson
2013-05-10 17:10 ` Matt Wilson
2013-05-13 9:51 ` Ian Campbell
2013-05-13 10:59 ` Christoph Egger
2013-05-13 20:32 ` Matt Wilson
2013-05-14 8:44 ` Ian Campbell
2013-05-14 9:09 ` Christoph Egger
2013-05-16 8:30 ` Matt Wilson
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=20130510124917.GA87221@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=chegger@amazon.de \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.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.