From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: stubdom: build failure
Date: Wed, 24 Sep 2008 15:48:45 +0200 [thread overview]
Message-ID: <20080924134845.GL4527@implementation.bordeaux.inria.fr> (raw)
In-Reply-To: <200809241539.26042.Christoph.Egger@amd.com>
Christoph Egger, le Wed 24 Sep 2008 15:39:25 +0200, a écrit :
> On Wednesday 24 September 2008 15:13:03 Samuel Thibault 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.
Ah... Well then the only way is to build a cross-compilation chain, as
was done before changetset 17969:433d1b26fd51 :/
Samuel
next prev parent reply other threads:[~2008-09-24 13:48 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 [this message]
2008-09-24 13:51 ` Keir Fraser
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=20080924134845.GL4527@implementation.bordeaux.inria.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=Christoph.Egger@amd.com \
--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.