From: Tim Deegan <tim@xen.org>
To: Matt Wilson <msw@amazon.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 1 of 2 v3] tools: check for documentation generation tools at configure time
Date: Tue, 18 Sep 2012 18:03:36 +0100 [thread overview]
Message-ID: <20120918170336.GA86732@ocelot.phlegethon.org> (raw)
In-Reply-To: <20120917170814.GA22382@u002268147cd4502c336d.ant.amazon.com>
At 10:08 -0700 on 17 Sep (1347876501), Matt Wilson wrote:
> While we're discussing expanding the coverage of ./configure, I
> wonder: what (if any) is the resistance to requiring ./configure to
> build the xen/ tree?
There's nothing in the hypervisor build that needs to be adjusted to
match the run-time userspace. So if you're a hypervisor maintainer it
just introduces all the charming idiosyncracies of autotools without
providing any benefit. E.g., this:
checking for yajl_alloc in -lyajl... no
configure: error: Could not find yajl
should not stop me building Xen. Also, as I said before, autoconf is
the thin end of a slippery wedge: the answer to any autotools problem is
always more autotools, and I choose to make my stand here rather than
have the argument later about why we shouldn't be using libtool. :)
Tim.
next prev parent reply other threads:[~2012-09-18 17:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 4:35 [PATCH 0 of 2 v3] improve checking for documentation tools and formatting Matt Wilson
2012-09-07 4:35 ` [PATCH 1 of 2 v3] tools: check for documentation generation tools at configure time Matt Wilson
2012-09-10 16:09 ` Ian Campbell
2012-09-10 20:46 ` Matt Wilson
2012-09-11 7:54 ` Ian Campbell
2012-09-11 19:00 ` Matt Wilson
2012-09-17 9:42 ` Ian Campbell
2012-09-17 17:08 ` Matt Wilson
2012-09-18 7:46 ` Ian Campbell
2012-09-18 9:49 ` Ian Jackson
2012-09-18 17:03 ` Tim Deegan [this message]
2012-09-07 4:35 ` [PATCH 2 of 2 v3] docs: use elinks to format markdown-generated html to text Matt Wilson
2012-09-07 8:51 ` [PATCH 0 of 2 v3] improve checking for documentation tools and formatting Ian Campbell
2012-09-07 20:28 ` Matt Wilson
2012-09-08 5:42 ` Ian Campbell
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=20120918170336.GA86732@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=msw@amazon.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).