| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 20 Jan 2013 14:21:26 -0500 From: Josh Boyer <jwboyer@...il.com> To: Suho Park <suho.hrvatska@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: Kernel 3.7.* Problerm On Sun, Jan 20, 2013 at 6:20 AM, Suho Park <suho.hrvatska@...il.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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists