From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] xen: Deal with stdarg.h and -nostdinc
Date: Fri, 27 May 2011 09:46:45 +0100
Message-ID: <CA052385.2DB18%keir@xen.org>
References: <4DDF590F.5040706@amd.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4DDF590F.5040706@amd.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

On 27/05/2011 08:55, "Christoph Egger" <Christoph.Egger@amd.com> wrote:

>> Not really. We are only doing the same as Linux right now. I do note that
>> they add an -isystem option to their command line, with a gcc include path
>> that they presumably dump out of gcc in some standard way. However, our
>> current approach seems to work, if it fails to work in some situation it is
>> likely to be pretty obvious (build or link failure), and we can fix it then.
> 
> The cross-compiling facility in NetBSD has been further improved which
> made gcc more pendantic for this. -nostdinc is used and -isystem is
> *not* used.

So where does NetBSD get its stdarg.h from in this case? It's somewhat bogus
to roll your own, as it contains compiler-specific intrinsics.

 -- Keir