Subject: Re: usage of ssp include files
To: None <email@example.com>
From: Christos Zoulas <firstname.lastname@example.org>
Date: 08/02/2007 09:33:43
In article <Pine.GSO.email@example.com>,
Krister Walfridsson <firstname.lastname@example.org> wrote:
>gcc fails to build on NetBSD 4 and current because of how the NetBSD SSP
>include files are handled (the gcc build process plays tricks with
>include paths, and files from GCC's SSP directory get included when the
>NetBSD string.h includes ssp/string.h). [*]
>This is obviously a gcc issue, and I usually do not advocate changing the
>OS to make other software's broken build processes to work, but I think
>it may make sense to fix this in our includes since this is after all a
>gcc feature we have added (besides, fixing this in NetBSD will make my
>life easier... ;)
>So, does it make sense to change our headers (current and netbsd-4) as
>the patch below?
>* It is possible to build by giving --disable-libssp to configure, but
> i think it is nice to be able to build a full gcc distribution, so
> that NetBSD users can use improvements that future gcc may introduce,
> and to benchmark against the NetBSD native version.
That change looks fine to me.