From: "Egger, Christoph" <chegger@amazon.de>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
tech mailinglists <mailinglists.tech@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: State of Stubdomains on NetBSD
Date: Wed, 8 May 2013 17:27:33 +0200 [thread overview]
Message-ID: <518A6EE5.5010206@amazon.de> (raw)
In-Reply-To: <20130508152002.GF8733@type.youpi.perso.aquilenet.fr>
On 08.05.13 17:20, Samuel Thibault wrote:
> Christoph Egger, le Wed 08 May 2013 12:37:57 +0200, a écrit :
>> On 07.02.13 12:03, Samuel Thibault wrote:
>>> Hello,
>>>
>>> tech mailinglists, le Thu 07 Feb 2013 11:56:39 +0100, a écrit :
>>>> I read in the wiki that stubdomains aren't support on NetBSD. Will subdoms be
>>>> supported on NetBSD? Is someone working on that topic actually?
>>>
>>> I see no reason why it should be hard to do it, so it should be just a
>>> matter of someone with a NetBSD box to just try and fix the few missing
>>> bits.
>>
>> It fails to build with 'stddef.h: No such file or directory'.
>> stddef.h is in /usr/include/ which is not part of the search-path.
>
> This is supposed to be coming from
>
> GCC_INSTALL = $(shell LANG=C gcc -print-search-dirs | sed -n -e 's/install: \(.*\)/\1/p')
> TARGET_CPPFLAGS += -isystem $(GCC_INSTALL)include
GCC_INSTALL is empty on NetBSD.
Christoph
next prev parent reply other threads:[~2013-05-08 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 10:56 State of Stubdomains on NetBSD tech mailinglists
2013-02-07 11:03 ` Samuel Thibault
2013-02-07 12:14 ` Samuel Thibault
2013-02-07 12:25 ` Roger Pau Monné
2013-02-07 12:28 ` tech mailinglists
2013-02-07 12:31 ` Samuel Thibault
2013-02-07 12:28 ` Samuel Thibault
2013-05-08 10:37 ` Christoph Egger
2013-05-08 15:20 ` Samuel Thibault
2013-05-08 15:27 ` Egger, Christoph [this message]
2013-05-08 15:34 ` Samuel Thibault
2013-02-07 11:05 ` [Xen-users] " Ian Campbell
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=518A6EE5.5010206@amazon.de \
--to=chegger@amazon.de \
--cc=mailinglists.tech@gmail.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xen.org \
/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.