From: Antti Kantee <pooka@iki.fi>
To: Ian Campbell <ian.campbell@citrix.com>, Wei Liu <wei.liu2@citrix.com>
Cc: Andrew Stuart <andrew.stuart@supercoders.com.au>,
xen-devel@lists.xen.org
Subject: Re: make c-stubdom returns No rule to make target `mini-os-x86_64-c'
Date: Thu, 16 Apr 2015 13:02:53 +0000 [thread overview]
Message-ID: <552FB2FD.8030700@iki.fi> (raw)
In-Reply-To: <1429179829.25195.61.camel@citrix.com>
On 16/04/15 10:23, Ian Campbell wrote:
> But I think we can safely(?) say that work done on rumpkernel will be a
> more worthwhile investment, while work on stubdom would be more of a
> sunk cost...
I can't speak for "stubdom", but I sure hope that work done on rump
kernels is a worthwhile investment ;)
One thing I'd like to note, though. While we certainly welcome users
and contributors already, until someone manages to get around to
whacking the build system enough to support an "install toolchain"
feature, it is unclear which bits in the build directory are meant to
remain stable and which ones just happened to be there at $t. If
someone wants to build systems and wants to depend on feature $x
remaining to be present, for now it's better to ask on the list.
http://wiki.rumpkernel.org/Info:-Community
- antti
next prev parent reply other threads:[~2015-04-16 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 8:32 make c-stubdom returns No rule to make target `mini-os-x86_64-c' Andrew Stuart
2015-04-16 9:10 ` Wei Liu
2015-04-16 9:39 ` Andrew Stuart
2015-04-16 10:17 ` Wei Liu
2015-04-16 10:23 ` Ian Campbell
2015-04-16 10:31 ` Wei Liu
2015-04-16 13:02 ` Antti Kantee [this message]
2015-04-16 10:48 ` Andrew Stuart
2015-04-16 10:50 ` Wei Liu
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=552FB2FD.8030700@iki.fi \
--to=pooka@iki.fi \
--cc=andrew.stuart@supercoders.com.au \
--cc=ian.campbell@citrix.com \
--cc=wei.liu2@citrix.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 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.