Messages in this thread | | | From | Thomas Horsten <> | Subject | Re: [PATCH] 2.4.21-rc1: byteorder.h breaks with __STRICT_ANSI__ defined (trivial) | Date | Wed, 7 May 2003 07:59:49 +0100 |
| |
On Wednesday 07 May 2003 7:45 am, Christoph Hellwig 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.
I don't see why moving up should be wrong - the ABI is {guaranteed | supposed} to remain backward compatible so the libc itself should be fine, and using the newer headers to build apps shouldn't hurt - at least I can't see any obvious cases (there are probably some, but at any rate I, have seen this work without problems a number of times, without rebuilding libc but using new features from the kernel, like iptables).
In any case, it doesn't change my example, just let Joe Admin rebuild glibc as well :-)
// Thomas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |