This is the mail archive of the
mailing list for the GCC project.
Re: [patch win32]: fix for PR target/41943
2010/7/22 Richard Guenther <email@example.com>:
> On Thu, Jul 22, 2010 at 1:42 PM, Kai Tietz <firstname.lastname@example.org> wrote:
>> 2010/7/22 Danny Smith <email@example.com>:
>>>>> c:\mingw\bin\../lib/gcc/mingw32/4.6.0/include/float.h:278:24: fatal error: float
>>>>> .h: No such file or directory
>>>>> compilation terminated.
>>>> I know. But as the float.h from gcc's internal header always comes
>>>> first in include order, this next_include in system-headers is wrong.
>>> mingw CRT and winapi headers have long been placed in the
>>> LOCAL_INCLUDE_DIR on window's hosts, since Windows doesn't really have
>>> a system include directory. ?This local include dir is defined as
>>> being relative to exec_prefix in x-mingw32.
>>> The local include dir is included before gcc's internal headers.
>> That's right and therefore I dislike this patch and would prefer to
>> have that one Ozkan mentioned already. The issue is that sysroot &
>> cross- includes come after gcc's internal header, which is causing the
>> pain that it isn't absolutely predicatable, if system-headers are
>> reached or not.
>> By changing the order of gcc's internal to the end of the include
>> chain, it would be solved for all cases.
> Well, I think moving gcc headers to the end of the include chain is
> just wrong. ?They are supposed to override host ones (which is
> why they are called "fixincludes"). ?Why not fixinclude mingw?
Because gcc's internal headers aren't the fixed-include ones. Secondly
the fixed-include headers coming after gcc's internal headers, so
using fixinclude leads nowhere and doesn't solve anything here.
|? (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination