Re: [PATCH] 2.4.21-rc1: byteorder.h breaks with __STRICT_ANSI__ defined (trivial)

[Christoph Hellwig <hch@infradead.org>]

On Tue, May 06, 2003 at 10:44:05PM -0700, David S. Miller wrote:
>    That's highly broken because his libc was compiled against 2.2
>    headers.  You must never use different headers in
>    /usr/include/Pasm,linux} then those your libc was compiled against.
>    
> While I understand this problem, this line of reasoning simply does
> not apply for headers that libc/glibc/whatever are agnostic about.

That's how it should be.  We had tons of problems due to mismatchig
headers (usually it was "just" compile breakage because older libc
headers / compilers couldn't cope with constructs used in new kernel
headers) in the past and the only way to fix this is really don't 
ever use mismatching headers.  This is not just related to kernels,
for example Oracle ()at least up to 8i) ships .o files for their product
that were compiled on some development box but then link them at
installation time to the user's system libc.  You can guess how this
breaks :)