Summary: | glibc-2.3.3.20040420 failed to compile complaining about asm/unistd.h many times | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lukas Kutner <xkutner> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED INVALID | ||
Severity: | critical | CC: | jared |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge output |
Description
Lukas Kutner
2004-06-07 07:14:38 UTC
Created attachment 32861 [details]
emerge output
well I changed my kernel to 2.6.5-love5 and it works now Same thing happens for me. It broke around the same time I did a linux-headers remerge and I can see a possible relationship given the "asm/unistd.h" error. I'm running 2.6.7 stock. Is it ok to be running linux-headers-2.4.22 when I'm running a 2.6 kernel? I can remerge linux-headers without problems, but not glibc. I do have a /usr/include/asm/unistd.h file in place. I will investigating issues related to my /usr/src tree. There's probably a problem in include directory there, or with one of the symlinks pointed there. A kernel rebuild/reinstall might do the trick. Yup, a kernel rebuild/install cycle fixed whatever include files and/or symlinks had gotten out of whack with my actual runtime, and glibc now emerges fine. Recommend closing this bug as not a bug. It's not in glibc, it's not in emerge, it's not reproducible. (Though I'm sure toolchain@gentoo.org already knew that :) The official workaround can be "reinstall the kernel". btw, linux-headers 2.6.6-r1 seems pretty bug-less. these are currently the suggested 2.6 headers. and no, it isnt a problem to use 2.4 headers while running a 2.6 kernel. |