|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] stubdom: build failure
On 24/9/08 14:39, "Christoph Egger" <Christoph.Egger@xxxxxxx> 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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] stubdom: build failure, Christoph Egger
- Re: [Xen-devel] stubdom: build failure, Samuel Thibault
- Re: [Xen-devel] stubdom: build failure, Christoph Egger
- Re: [Xen-devel] stubdom: build failure, Samuel Thibault
- Re: [Xen-devel] stubdom: build failure, Christoph Egger
- Re: [Xen-devel] stubdom: build failure, Samuel Thibault
- Re: [Xen-devel] stubdom: build failure, Christoph Egger
- Re: [Xen-devel] stubdom: build failure, Samuel Thibault
- Re: [Xen-devel] stubdom: build failure,
Keir Fraser <=
- Re: [Xen-devel] stubdom: build failure, Christoph Egger
- Re: [Xen-devel] stubdom: build failure, Keir Fraser
- Re: [Xen-devel] stubdom: build failure, Samuel Thibault
- Re: [Xen-devel] stubdom: build failure, Christoph Egger
- Re: [Xen-devel] stubdom: build failure, Samuel Thibault
- Re: [Xen-devel] stubdom: build failure, Keir Fraser
- Re: [Xen-devel] stubdom: build failure, Samuel Thibault
- Re: [Xen-devel] stubdom: build failure, Samuel Thibault
|
|
|
|
|