From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: stubdom: build failure Date: Wed, 24 Sep 2008 14:51:38 +0100 Message-ID: References: <200809241539.26042.Christoph.Egger@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200809241539.26042.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 14:39, "Christoph Egger" 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? I assume it might cause us to put more headers in the search path than we'd like. -- Keir