From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: stubdom: build failure Date: Wed, 24 Sep 2008 15:31:13 +0100 Message-ID: References: <200809241621.22646.Christoph.Egger@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200809241621.22646.Christoph.Egger@amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Christoph Egger , xen-devel@lists.xensource.com Cc: Samuel Thibault List-Id: xen-devel@lists.xenproject.org On 24/9/08 15:21, "Christoph Egger" 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