| 1 | <sect2><title> </title><para> </para></sect2>
|
|---|
| 2 |
|
|---|
| 3 | <sect2>
|
|---|
| 4 | <title>Installation of the kernel headers</title>
|
|---|
| 5 |
|
|---|
| 6 | <para>We won't be compiling a new kernel yet -- we'll do that when we have
|
|---|
| 7 | finished the installation of all the packages. But as some packages need the
|
|---|
| 8 | kernel header files, we're going to unpack the kernel archive now, set it up
|
|---|
| 9 | and copy the header files so they can be found by these packages.</para>
|
|---|
| 10 |
|
|---|
| 11 | <para>It is important to note that the files in the kernel source directory
|
|---|
| 12 | are not owned by <emphasis>root</emphasis>. Whenever you unpack a package as
|
|---|
| 13 | user <emphasis>root</emphasis> (like we do here inside chroot), the files end
|
|---|
| 14 | up having the user and group IDs of whatever they were on the packager's
|
|---|
| 15 | computer. This is usually not a
|
|---|
| 16 | problem for any other package you install because you remove the source
|
|---|
| 17 | tree after the installation. But the Linux kernel source tree is often kept
|
|---|
| 18 | around for a long time, so there's a chance that whatever user ID the packager
|
|---|
| 19 | used will be assigned to somebody on your machine and then that person would
|
|---|
| 20 | have write access to the kernel source.</para>
|
|---|
| 21 |
|
|---|
| 22 | <para>In light of this, you might want to run <userinput>chown -R 0:0</userinput>
|
|---|
| 23 | on the <filename>linux-&kernel-version;</filename> directory
|
|---|
| 24 | to ensure all files are owned by user <emphasis>root</emphasis>.</para>
|
|---|
| 25 |
|
|---|
| 26 | <para>Prepare for header installation:</para>
|
|---|
| 27 |
|
|---|
| 28 | <para><screen><userinput>make mrproper</userinput></screen></para>
|
|---|
| 29 |
|
|---|
| 30 | <para>This ensures that the kernel tree is absolutely clean. The kernel team
|
|---|
| 31 | recommends that this command be issued prior to <emphasis>each</emphasis> kernel
|
|---|
| 32 | compilation. You shouldn't rely on the source tree being clean after
|
|---|
| 33 | untarring.</para>
|
|---|
| 34 |
|
|---|
| 35 | <para>Create the <filename>include/linux/version.h</filename> file:</para>
|
|---|
| 36 |
|
|---|
| 37 | <para><screen><userinput>make include/linux/version.h</userinput></screen></para>
|
|---|
| 38 |
|
|---|
| 39 | <para>Create the platform-specific <filename>include/asm</filename>
|
|---|
| 40 | symlink:</para>
|
|---|
| 41 |
|
|---|
| 42 | <para><screen><userinput>make symlinks</userinput></screen></para>
|
|---|
| 43 |
|
|---|
| 44 | <para>Install the platform specific-header files:</para>
|
|---|
| 45 |
|
|---|
| 46 | <para><screen><userinput>cp -HR include/asm /usr/include
|
|---|
| 47 | cp -R include/asm-generic /usr/include</userinput></screen></para>
|
|---|
| 48 |
|
|---|
| 49 | <para>Install the cross-platform kernel header files:</para>
|
|---|
| 50 |
|
|---|
| 51 | <para><screen><userinput>cp -R include/linux /usr/include</userinput></screen></para>
|
|---|
| 52 |
|
|---|
| 53 | <para>There are a few kernel header files which make use of the
|
|---|
| 54 | <filename>autoconf.h</filename> header file. Since we do not yet configure the
|
|---|
| 55 | kernel, we need to create this file ourselves in order to avoid compilation
|
|---|
| 56 | failures. Create an empty <filename>autoconf.h</filename> file:</para>
|
|---|
| 57 |
|
|---|
| 58 | <para><screen><userinput>touch /usr/include/linux/autoconf.h</userinput></screen></para>
|
|---|
| 59 |
|
|---|
| 60 | </sect2>
|
|---|
| 61 |
|
|---|
