This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] stubdom: build failure

Christoph Egger, le Wed 24 Sep 2008 16:43:34 +0200, a écrit :
> On Wednesday 24 September 2008 16:35:58 Samuel Thibault wrote:
> > Keir Fraser, le Wed 24 Sep 2008 15:31:13 +0100, a écrit :
> > > If it's due to pulling in too many /usr/include headers then perhaps
> > > we could copy the ones we actually need into a private local directory
> > > and add that to the search path instead? I guess it depends if those
> > > headers themselves #include any more; then it'd get messy. If they're
> > > compiler intrinsics then perhaps they won't.
> >
> > In principles we only needs files that declare compiler intrinsics.
> On NetBSD, compiler intrinsics don't exist.
> I think, it's better to put an OS abstraction into stubdom where
> only the Linux specific code uses compiler intrinsics and other Linux-only 
> stuff.
> If you try (hard) to make every OS look like Linux instead, things become 
> messy.

That's not the problem. We already do make mini-os have its own
definitions etc.  What we don't want to do is to define things like
stdarg.h and such, thus including these gcc headers (what we call gcc
intrinsics).  Before cs 17969:433d1b26fd51, we were not using the host
headers and compiler at all and building a full cross-compilation
environment instead; but that takes quite some time, while we already
have a compiler on the host...


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>