From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Christoph Egger <Christoph.Egger@amd.com>, xen-devel@lists.xensource.com
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: stubdom: build failure
Date: Wed, 24 Sep 2008 14:51:38 +0100 [thread overview]
Message-ID: <C500047A.27708%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <200809241539.26042.Christoph.Egger@amd.com>
On 24/9/08 14:39, "Christoph Egger" <Christoph.Egger@amd.com> 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
next prev parent reply other threads:[~2008-09-24 13:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 12:25 stubdom: build failure Christoph Egger
2008-09-24 12:33 ` Samuel Thibault
2008-09-24 12:40 ` Christoph Egger
2008-09-24 12:48 ` Samuel Thibault
2008-09-24 12:57 ` Christoph Egger
2008-09-24 13:13 ` Samuel Thibault
2008-09-24 13:39 ` Christoph Egger
2008-09-24 13:48 ` Samuel Thibault
2008-09-24 13:51 ` Keir Fraser [this message]
2008-09-24 14:21 ` Christoph Egger
2008-09-24 14:31 ` Keir Fraser
2008-09-24 14:35 ` Samuel Thibault
2008-09-24 14:43 ` Christoph Egger
2008-09-24 14:51 ` Samuel Thibault
2008-09-24 15:02 ` Keir Fraser
2008-09-24 14:35 ` Samuel Thibault
2008-09-24 14:24 ` Samuel Thibault
-- strict thread matches above, loose matches on Subject: below --
2008-10-03 0:23 Stubdom " Neo Jia
2009-07-29 14:37 stubdom " George Dunlap
2009-07-29 14:55 ` Stefano Stabellini
2009-07-29 15:07 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C500047A.27708%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Christoph.Egger@amd.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.