source: chapter05/kernel-inst.xml@ 7fd5797

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.0 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk v3_0 v3_1 v3_2 v3_3 v4_0 v4_1 v5_0 v5_1 v5_1_1 xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 7fd5797 was 5aa8b71, checked in by Simon Perreault <nomis80@…>, 23 years ago

Added FHS compliance notes regarding the use of symlinks for the kernel header directories.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@564 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 1.6 KB
Line 
1<sect2>
2<title>Installation of Linux Kernel</title>
3
4<para>
5We won't be compiling a new kernel image yet. We'll do that after we
6have finished the installation of the basic system software in this
7chapter. But because certain software need the kernel header files, we're
8going to unpack the kernel archive now and set it up so that we can
9compile package that need the kernel.
10</para>
11
12<para>
13The kernel configuration file is created by running the following command:
14</para>
15
16<blockquote><literallayout>
17 <userinput>make mrproper &amp;&amp;</userinput>
18 <userinput>yes "" | make config &amp;&amp;</userinput>
19 <userinput>make dep &amp;&amp;</userinput>
20 <userinput>cd $LFS/usr/include &amp;&amp;</userinput>
21 <userinput>ln -s ../src/linux/include/linux &amp;&amp;</userinput>
22 <userinput>ln -s ../src/linux/include/asm</userinput>
23</literallayout></blockquote>
24
25</sect2>
26
27<sect2>
28<title>FHS compliance notes</title>
29
30<para>
31According to the FHS, the /usr/include/linux and /usr/include/asm should be
32actual directories, not symbolic links to the ones belonging to the current
33kernel. The major advantage is that programs will compile with the headers glibc
34was compiled with, and this may prevent some compiling hell. Until now, in all
35of LFS' history, no compiling problem has been reported by using symlinks. So if
36you're tight on space, we recommend using symlinks. But if you want to be FHS
37compliant, replace the two last lines from the commands above with those:
38</para>
39
40<blockquote><literallayout>
41 <userinput>cp -r ../src/linux/include/linux . &amp;&amp;</userinput>
42 <userinput>cp -r ../src/linux/include/asm .</userinput>
43</literallayout></blockquote>
44
45</sect2>
46
Note: See TracBrowser for help on using the repository browser.