Summary: | glibc-2.3.5-r1 emerge failure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Samuele Kaplun <Samuele.Kaplun> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | CC: | vitti93 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Samuele Kaplun
2005-07-28 02:12:24 UTC
Umh... I think it's a linux-headers related bug, because I was able to emerge when I returned to the standard linux-headers-2.6.11-r2. Previously, I was using direct headers from my own versions of kernel (I tried vanilla-2.6.13-rc3, gentoo-2.6.12-r6, ck-overloaded-2.6.12-cko3 without success... so I assume there's a problem in the headers of linux-2.6.12...) you are right this is INVALID, but not that the linux headers are broken the kernel maintainers atm are not cleaning up their headers so that they can be used by userspace ... that is why you should *never* symlink your /usr/include/{linux,asm} dirs to your live kernel use the linux-headers ebuilds, we santize the headers for you But what if other packages search for bleeding edge feature of last kernels? *** Bug 259375 has been marked as a duplicate of this bug. *** |