From: Suho Park <suho.hrvatska@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel 3.7.* Problerm
Date: Sun, 20 Jan 2013 20:20:03 +0900 [thread overview]
Message-ID: <20130120202003.46105e04704f19f219d6373e@gmail.com> (raw)
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
++++++++++++++++++++++++++
next reply other threads:[~2013-01-20 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 11:20 Suho Park [this message]
2013-01-20 19:21 ` Josh Boyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130120202003.46105e04704f19f219d6373e@gmail.com \
--to=suho.hrvatska@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome