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: PING Re: [PATCH] do not install float.h, stddef.h and stdarg.h for mingw-w64

From: Pedro Alves <pedro at codesourcery dot com>
To: gcc-patches at gcc dot gnu dot org
Cc: Kai Tietz <ktietz70 at googlemail dot com>, Danny Smith <dansmister at gmail dot com>, Ozkan Sezer <sezeroz at gmail dot com>, NightStrike <nightstrike at gmail dot com>, Dave Korn <dave dot korn dot cygwin at googlemail dot com>
Date: Thu, 15 Apr 2010 10:48:53 +0100
Subject: Re: PING Re: [PATCH] do not install float.h, stddef.h and stdarg.h for mingw-w64
References: <i2s647fe9b11004142301r8127d10dm4834b5321546254@mail.gmail.com> <i2q9c03c2dd1004150045nc4b403b6he6434adec2af7d5b@mail.gmail.com> <o2l90baa01f1004150137x6412dfawb8098c73d033a1c7@mail.gmail.com>

We had a similar discussion related to limits.h over at mingw32ce
a while ago. Wasn't the real problem that fact that the mingw* build
process does not fixinclude mingw headers, ever?  Shouldn't
fixincludes pick up these system headers if they exist and wrap them
with whatever gcc glue gcc wants?  Isn't that what other systems do
to handle this?

-- 
Pedro Alves

References:
- Re: PING Re: [PATCH] do not install float.h, stddef.h and stdarg.h for mingw-w64
  - From: Ozkan Sezer
- Re: PING Re: [PATCH] do not install float.h, stddef.h and stdarg.h for mingw-w64
  - From: Danny Smith
- Re: PING Re: [PATCH] do not install float.h, stddef.h and stdarg.h for mingw-w64
  - From: Kai Tietz

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