Messages in this thread | | | Date | Wed, 7 May 2003 07:45:57 +0100 | From | Christoph Hellwig <> | Subject | Re: [PATCH] 2.4.21-rc1: byteorder.h breaks with __STRICT_ANSI__ defined (trivial) |
| |
On Wed, May 07, 2003 at 07:44:27AM +0100, Thomas Horsten wrote: > However I do not agree with that - I think it makes total sense for userland > to include kernel headers when we are talking e.g. specific device driver > interface. Imagine Joe Admin has firewall which is a pretty old Slackware > with 2.2 kernel and wants to upgrade to 2.4 to get from ipchains to iptables > (all just an example). He just downloads the 2.4 kernel and builds it, > symlinks to /usr/src/linux so his /usr/include/linux and ../asm will point to > the new kernel then he goes on to build the iptables userland binary - oops,
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.
- 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/
| |