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] [PATCH] Correct public header defines for Solaris/Sun CC

To: Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Correct public header defines for Solaris/Sun CC
From: John Levon <john.levon@xxxxxxx>
Date: Thu, 9 Aug 2007 11:50:09 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 09 Aug 2007 03:46:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2E09818.13DC7%keir@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <24eb50ea28dea351633c.1186596260@xenbld> <C2E09818.13DC7%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
On Thu, Aug 09, 2007 at 10:08:24AM +0100, Keir Fraser wrote:

> On 8/8/07 19:04, "john.levon@xxxxxxx" <john.levon@xxxxxxx> wrote:
> > Correct public header defines for Solaris/Sun CC
> > 
> > The Solaris environment only defines __i386, not __i386__.
> > Additionally, the assembler define used is _ASM. Accommodate both.
> Can't you just include xen.h through a wrapper that makes these definitions
> for your non-gnu environment? Since I assume this is for Solaris and so you
> have full control over the source code of the includer.

Well that's what we're doing now. But there are two disadvantages here:

1) we have to maintain these changes indefinitely and make sure everything goes
through this wrapper. Extra-upstream changes suck and we do our best to avoid
them wherever we can.

2) the wrapper only applies to the kernel, whereas these headers are used in
userspace too. Whilst there's no immediate intention of compiling the Xen
sources themselves with Sun CC, it seems unnecessarily sharp to prevent any
tools from using these headers directly in such an environment

And finally, it's not a large or particularly ugly change...


Xen-devel mailing list

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