On Sat, May 30, 2015 at 10:12:48PM +0200, Richard Weinberger wrote: > On Sat, May 30, 2015 at 5:37 PM, Mikko Rapeli <mikko.rap...@iki.fi> wrote: > > v3: > > tried to fix all v2 review findings > > tried to guess how to fix a few more issue > > with a few hacks, 0 files fail and 760 files pass the compile test on 32bit > > x86 > > > > v2: > > https://lkml.org/lkml/2015/2/16/521 > > added cross compiler support with CROSS_COMPILE, > > detecting libc and GCC headers from compiler, > > more header file fixes > > > > v1: > > https://lkml.org/lkml/2014/8/21/665 > > > > Users of kernel header files would be happier if they did not contain > > kernel specific parts and would contain #include statements for all > > other header files that they depend on, and in general would compile. > > Maybe this is a stupid question, but does that mean that many of our uapi > headers never worked as expected and don't build at all?
Yes. Many uapi headers do not compile in userspace and users of those headers need to either copy stuff out or do other tricks when including them. See patch nr 0002 for stats, or https://lkml.org/lkml/2015/5/30/98 -Mikko -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
