On Jun 3, 2012, at 7:45 AM, Jonathan Wakely wrote:
> It's trivial to let it run and compare the fixed files to the
> originals. On my system with a recent glibc I still see lots of
> changes to limits.h, I assume they're not pointless and are worth
> having.
I believe that gcc always supplies an
On 6/2/12 5:34 PM, Eric Botcazou wrote:
What are you after, exactly? Even on modern OSes, there might be glitches or
small incompatibilities that woud need to be fixed in order for GCC to work
properly, and fixincludes is the tried and proven tool to do that. It is
designed to modify only what
On May 28, 2012, at 7:25 PM, Jonathan Wakely wrote:
> The "upstream packages" might be a third-party OS vendor who supply
> their own compiler and have no interest in supporting GCC. Even if the
> OS system headers get changed, that doesn't help users who have the
> unchanged version (e.g. someon
Hello,
I'm endeavoring to understand the history and purpose of the fixincludes
script. The README-fixinc states that the purpose is to fix
ANSI-incompatible headers which 'many vendors supply'. Is this really
still the case? Certainly by now this is very rare and corner cases
should really b
