Summary: | base system: kernel headers / glibc inconsistency | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Reporter <hans.w.wurst> |
Component: | [OLD] Core system | Assignee: | Please assign to toolchain <gcc-porting> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 27636 | ||
Bug Blocks: |
Description
Reporter
2003-08-03 15:39:33 UTC
Hmm, a good thought. I think what I'll do is add a small note to linux-headers-2.4.21 informing people it would be "wise" to re-merge glibc following the update of kernel headers. linux-headers-2.4.21 is current in unstable for most archs, and should go stable soon (hopefully), so it would be a good thing to add. The other solution is to make glibc depend on newer headers, and I'm unsure how this change would affect things. The newer header ebuilds utilize kernel.eclass, and thus when merging on a stage1 system, when you pull in linux-headers, the system attempts to merge about 20 other packages beforehand. Hopefully with the advent of new stages for the various archs, this will no longer be an issue, as I do not forsee any move to linux-headers-2.4.22 in the near future until the iputils issue is resolved. I'll go ahead and resolve this bug and add the note to linux-headers-2.4.21 and 2.4.22 ebuilds shortly. |