Opened 11 years ago
Closed 11 years ago
#3506 closed task (fixed)
contradictory wording about system headers
| Reported by: | Joel Kammet | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.6 |
| Component: | Book | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description
The very last comment ("Warning ...") at the end of Section 8.3.1 seems self-contradictory:
"The headers in the system's include directory should always be the ones against which Glibc was compiled, that is, the sanitised headers from this Linux kernel tarball. Therefore, they should never be replaced by either the raw kernel headers or any other kernel sanitized headers."
The "system's include directory", I take it, is our new LFS system in /mnt/lfs/include, i.e., NOT the headers in the kernel tarball.
Shouldn't "that is," be replaced with "not"? Also, perhaps eliminate any ambiguity by replacing (in the last sentence) "they" with "the system headers".
Note:
See TracTickets
for help on using tickets.
The system's 'include directory' is the new /usr/include/linux that we installed in Section 6.7. Linux-3.13.3 API Headers. That's what we built glibc against.
The 'raw kernel headers' are those in the tarball.
We can clarify the note.