Re: wait.h warnings from gpmevent.c
Valdis.Kletnieks(a)vt.edu writes:
Is this brought to you by the same crew that brought us the infamous
gcc fuxincludes, where the compiler thought they knew better than
the system what system header files should look like, and punished non
compliant systems by breaking on every patch that hit /usr/include? ;)
It's a different crew. Fixincludes are necessary for GCC because
vendor include files contain vendor specific extensions (and bugs)
that only works on the vendor specific compiler. So it is either
fixincludes, no system includes, or using the vendor compiler.
Alternatively, GCC could implement every extension and support every
bug that have ever existed in a Unix system compiler.
If fixincludes is necessary with glibc include files it is silly,
since the "vendor compiler" for glibc is GCC.
/Valdis (who is trying to move from an AIX to Linux, and wondering
how
much brain-damage he's willing to accept as the cost of price/performace ;)
Basically, from the point of view of the GNU tools, anything is better
than AIX. AIX is the most non-standard Unix system. Currently, AIX
support seems to be the major thing holding back the GCC 3.0 release.