This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] do not install float.h, stddef.h and stdarg.h for mingw-w64


On Tue, Jan 19, 2010 at 11:02 AM, Kai Tietz <ktietz70@googlemail.com> wrote:
> 2010/1/19 Paolo Carlini <pcarlini@gmail.com>:
>> Hi,
>>
>>> Hi:
>>>
>>> The mingw-w64 header set already provides float.h, stdarg.h and
>>> stddef.h with their own additions. The attached patch makes gcc
>>> to not install those headers for *-w64-mingw*. Please consider
>>> for applying to 4.5. (I don't have write permissions. The patch
>>> file has the ChangeLog.)
>>
>> Hummm. Now I have a question for the GWPs or in any case any maintainer
>> knowing well the full range if targets which we are supporting: is the above
>> request normal? Naively, I was thinking ?that GCC installs *everywhere*
>> float.h, as happens on Linux, for example. *If* that were true tweaking it a
>> bit, eg, for decimal floating point in C++ would be so easy...
>
> We would prefer to use GCC's basic headers here and we would like to
> avoid the double work of maintaining duplicates headers with some, but
> for -w64- target important, extensions. We tried in the near past an
> attempt to add target specific next-includes to those headers, but
> failed badly to get this into gcc. So we see at the moment no other
> way to give our users a working gcc OOTB with for the target required
> behavior.
> We were forced to this step by many user bug-report we got in
> mingw-w64 about the incompatible behavior of stddef.h, float.h, and
> stdarg.h of gcc.
>

#include_next doesn't work for you?


-- 
H.J.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]