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: Christoph Egger <Christoph.Egger@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] stubdom: build failure
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 24 Sep 2008 15:31:13 +0100
Cc: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>
Delivery-date: Wed, 24 Sep 2008 07:31:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200809241621.22646.Christoph.Egger@xxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckeUjHkcG6TcIpFEd2egwAX8io7RQ==
Thread-topic: [Xen-devel] stubdom: build failure
User-agent: Microsoft-Entourage/
On 24/9/08 15:21, "Christoph Egger" <Christoph.Egger@xxxxxxx> wrote:

>> 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? I assume it might
>> cause us to put more headers in the search path than we'd like.
> Since the buildsystem appends include automatically, I tested with
> forcing GCC_INSTALL="/usr/"
> This fixed the problem about not finding stddef.h , but shows
> other errors then:

Hopefully Samuel has an idea what's going on here. 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.

 -- Keir

Xen-devel mailing list