From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
Christoph Egger <Christoph.Egger@amd.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] minios: minor buildsystem fixes
Date: Wed, 15 Jul 2009 13:39:31 +0100 [thread overview]
Message-ID: <C6838C93.F994%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0907151331190.1682@kaball-desktop>
On 15/07/2009 13:35, "Stefano Stabellini" <Stefano.Stabellini@eu.citrix.com>
wrote:
>> The new infrastructure I have in mind will allow to choose if you use
>> newlib, libz, lwip and pciutils or use the native libs from the
>> base system.
>>
>> Linux build will default to first, NetBSD build will default to latter one.
>
> I like the idea, could you please explain with a little bit more details
> how the crossbuilding works on NetBSD?
> Would it be possible to use NetBSD libc instead of newlib even on Linux?
>
> However Keir is right about XEN_OS: the stubdom Makefile
> shouldn't change it but should only set CONFIG_MiniOS instead.
If the distinction that Christoph's patch introduced *were* to be required,
I would do it as XEN_COMPILE_OS and XEN_TARGET_OS replacing XEN_OS. Arguably
it would be clearer to rename existing XEN_OS to the former anyway?
-- Keir
next prev parent reply other threads:[~2009-07-15 12:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 9:42 [PATCH] minios: minor buildsystem fixes Christoph Egger
2009-07-15 10:40 ` Keir Fraser
2009-07-15 12:27 ` Christoph Egger
2009-07-15 12:35 ` Stefano Stabellini
2009-07-15 12:39 ` Keir Fraser [this message]
2009-07-15 12:43 ` Stefano Stabellini
2009-07-15 12:59 ` Keir Fraser
2009-07-15 14:54 ` Christoph Egger
2009-07-15 16:03 ` Ian Jackson
2009-07-15 16:13 ` Stefano Stabellini
2009-07-15 17:24 ` Samuel Thibault
2009-07-16 12:17 ` Christoph Egger
2009-07-16 13:46 ` Samuel Thibault
2009-07-16 13:53 ` Ian Jackson
2009-07-15 16:39 ` Stefano Stabellini
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=C6838C93.F994%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Christoph.Egger@amd.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xensource.com \
/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.