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

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] stubdom: build failure
From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>
Date: Wed, 24 Sep 2008 16:24:09 +0200
Cc: Christoph Egger <Christoph.Egger@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 24 Sep 2008 07:24:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C500047A.27708%keir.fraser@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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Christoph Egger <Christoph.Egger@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
References: <200809241539.26042.Christoph.Egger@xxxxxxx> <C500047A.27708%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.12-2006-07-14
Keir Fraser, le Wed 24 Sep 2008 14:51:38 +0100, a écrit :
> On 24/9/08 14:39, "Christoph Egger" <Christoph.Egger@xxxxxxx> wrote:
> >> Uh, it's odd that -print-search-dirs doesn't provide the install one.
> >> Does gcc -print-file-name=include/stddef.h provide the correct path?
> > 
> > No. gcc -print-file-name=blah  works like  echo blah
> > On NetBSD there are only system libs and headers.
> > 
> > On NetBSD stddef.h is in /usr/include/  as well as
> > stdarg.h, stdbool.h, etc.
> Could we perhaps force GCC_INSTALL to /usr/include on BSD systems? Or if
> GCC_INSTALL is empty after executing the current shell runes?
> Can you check forcing GCC_INSTALL=/usr/include works?

Please do yes, and if it works then great.

> I assume it might cause us to put more headers in the search path than
> we'd like.

In principle the mini-os ones should get before that, but at least by
including stddef.h and such we might pull libc headers and thus pull
compilation issues. Let's see.


Xen-devel mailing list

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