Opened 18 years ago
Closed 18 years ago
#2024 closed task (fixed)
Bad outcome of make headers_install
Reported by: | Marty Jack | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Book | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
When 2.6.21 came out, I decided to install new kernel headers. I learned that if you do make INSTALL_HDR_PATH=/usr headers_install over top of a finished system, it destroys everything in /usr/include other than what make headers_install thinks should be there.
This was expensive to fix. I think a note in the book not to do that would be a good idea. There are other means to this end such as installing to a temporary directory and cp -R; although it's also arguable that if you want new kernel headers, the only sane way to do it is as part of a fresh start.
-- Marty Jack
Change History (2)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed in r8147 via placing that para on a separate warning a changing a bit the wording.
If you want new kernel headers, you need to recompile glibc. And once you do that, you pretty much have to recompile the whole system.
DO NOT try to upgrade the kernel headers, in other words!
Also see the last paragraph in the warning on this page in the book:
http://www.linuxfromscratch.org/lfs/view/development/chapter08/kernel.html
and note the requirement that the headers be the same ones that glibc was compiled against.