Kernel 3.7.* Problerm

Kernel 3.7.* Problerm

[Suho Park]

I used the following method since 2.4 version
1. copy .config from the old kernel
2. make oldconfig
(2-1. make dep)
3. make && make modules && make modules_install && make install
and then change the symbolic link of kernel header in /usr/include
to the compiled kernel header.
Works well from 2.4.0 up to 3.6.11

The problem is that 
3.6.11----->3.7.0 is OK
3.7.0 ----->3.7.1 not OK
3.7.1----->3.7.3 not OK

The point is that kerhel header is devided
into two parts linux/include/linux,
linux/include/uapi/linux.

The solution is that I always change the kernel
header includes to point 3.6.11, and compile 3.7.3

There are many applications using linux kernel header,
and I add the following in Makefile
-I/usr/include/uapi, where uapi is symbolically linked to
the kernel/include/uapi, for example I tested netfilter.

Is there any good reason of the division of the kernel headers?
Or is there any good solution?.

-- 
++++++++++++++++++++++++++
Suho Park(suhopark@math.snu.ac.kr)
+82-10-3450-6216
++++++++++++++++++++++++++

Re: Kernel 3.7.* Problerm

[Josh Boyer]

On Sun, Jan 20, 2013 at 6:20 AM, Suho Park <suho.hrvatska@gmail.com> wrote:
> I used the following method since 2.4 version
> 1. copy .config from the old kernel
> 2. make oldconfig
> (2-1. make dep)
> 3. make && make modules && make modules_install && make install
> and then change the symbolic link of kernel header in /usr/include
> to the compiled kernel header.
> Works well from 2.4.0 up to 3.6.11

There is a "headers_install" make target that will actually install the
kernel headers in a sanitized fashion onto your machine.  Linking
to the raw kernel header files isn't recommended at all.  The resulting
headers from this target are explicitly supposed to be for userspace to
include, without getting conflicts or kernel-internal definitions
included.

> There are many applications using linux kernel header,
> and I add the following in Makefile
> -I/usr/include/uapi, where uapi is symbolically linked to
> the kernel/include/uapi, for example I tested netfilter.
>
> Is there any good reason of the division of the kernel headers?
> Or is there any good solution?.

Use the headers_install target.

josh