Summary: | glibc-2.4-r4 fails build with glibc-compat20 use flag | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | brad walker <bradmwalker> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | beschindler, che, gentoo, mistatengwar, voyageur |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | debug output for failed glibc-2.4-r4 |
Description
brad walker
2006-09-29 22:01:40 UTC
Created attachment 98426 [details]
debug output for failed glibc-2.4-r4
squirrel ~ # FEATURES="installsources" emerge -dav glibc &> glibc-2.4-r4-failure.txt
yes
squirrel ~ #
did you even read the error message ? The error message is uninformative at best, I had to read the ebuild to understand that the glibc-compat20 USE flag was responsible! Explaining this instead of ranting on broken old apps would have been much better I had this flag on a year ago for an app to test for work, and did not remove it since I did not want to bother recompiling glibc to remove some compat code. Just a thought, what is the point of providing a USE flag which only use is now to cause a failed emerge?? i hadn't paid attention to glibc's use flag and i thought it was a new feature that might fix binary apps. whoops :) wouldn't it be better to test if glibc had previously been compiled with the flag? or even better, figure out what apps require a diff glibc and change their depends. *** Bug 149775 has been marked as a duplicate of this bug. *** *** Bug 150016 has been marked as a duplicate of this bug. *** *** Bug 198657 has been marked as a duplicate of this bug. *** |