source: chapter06/kernel-exp-headers.xml@ 5763f675

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 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 5763f675 was 4fa86d1, checked in by Greg Schafer <greg@…>, 21 years ago

Chapter 5 - Glibc: Add notes regarding test suite issues.

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

  • Property mode set to 100644
File size: 2.0 KB
RevLine 
[ef2b63b]1<sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
2
[1987d72]3<sect2>
4<title>Why we copy the kernel headers and don't symlink them</title>
5
[bed61bb]6<para>In the past it was common practice to symlink the
7<filename class="directory">/usr/include/{linux,asm}</filename> directories
8to <filename class="directory">/usr/src/linux/include/{linux,asm}</filename>.
9This was a <emphasis>bad</emphasis> practice, as the following extract from a
10post by Linus Torvalds to the Linux Kernel Mailing List points out:</para>
[1987d72]11
12<screen>I would suggest that people who compile new kernels should:
13
14 - not have a single symbolic link in sight (except the one that the
15 kernel build itself sets up, namely the "linux/include/asm" symlink
16 that is only used for the internal kernel compile itself)
17
18And yes, this is what I do. My /usr/src/linux still has the old 2.2.13
19header files, even though I haven't run a 2.2.13 kernel in a _loong_
[4fa86d1]20time. But those headers were what Glibc was compiled against, so those
[1987d72]21headers are what matches the library object files.
22
23And this is actually what has been the suggested environment for at
24least the last five years. I don't know why the symlink business keeps
25on living on, like a bad zombie. Pretty much every distribution still
26has that broken symlink, and people still remember that the linux
27sources should go into "/usr/src/linux" even though that hasn't been
28true in a _loong_ time.</screen>
29
[bed61bb]30<para>The essential part is where Linus states that the header files should be
[4fa86d1]31<emphasis>the ones which Glibc was compiled against</emphasis>. These are
[bed61bb]32the headers that should be used when you later compile other packages, as they
33are the ones that match the object-code library files. By copying the headers,
34we ensure that they remain available if later you upgrade your kernel.</para>
35
36<para>Note, by the way, that it is perfectly all right to have the kernel sources
37in <filename class="directory">/usr/src/linux</filename>, as long as you don't
38have the <filename class="directory">/usr/include/{linux,asm}</filename>
39symlinks.</para>
[1987d72]40
41</sect2>
[bed61bb]42
Note: See TracBrowser for help on using the repository browser.