Re: [Xen-devel] [PATCH] minios: minor buildsystem fixes

[Christoph Egger <Christoph.Egger@xxxxxxx>]

On Wednesday 15 July 2009 12:40:22 Keir Fraser wrote:
> On 15/07/2009 10:42, "Christoph Egger" <Christoph.Egger@xxxxxxx> wrote:
> > Attached patch changes MiniOS.mk and tools/Rules.mk
> > use the OS settings we build on.
> >
> > Signed-off-by: Christoph Egger <Christoph.Egger@xxxxxxx>
>
> This may need some thought. Using XEN_OS in some places and open coding
> 'uname -s' in others is just not nice and is fragile.
>
> Since stubdom is not being built in its own chroot, does it make sense for
> it to override XEN_OS at all? Should we keep that as 'build host OS'? The
> change around LFS in tools/Rules.mk could be indicative of a deeper issue
> -- information about arbitrary (non-GNU) host environments leaking into
> binaries which are actually targetting GNUish minios. Can the current
> approach work safely for NetBSD, Solaris, ... build hosts?
>
> So I throw this one to Stefano/Samuel. ;-)

The current approach works for Linux only.
NetBSD's base system is designed for cross-building.
My roadmap is to change the way how to build mini-os/stubdom
fundamentally:

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.

NetBSD libc doesn't have linux integer types, that's why mini-os
has been moved to C99 integer types. The mini-os headers need
some re-structuring to not conflict with the native libc, namely
if you want a mini-os header you explicitely have to type
<mini-os/header.h>

Christoph


-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel