| Summary: | failure to build kde-base/kdelibs-4.3.1-r2 on target kdeui_automoc | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | bagas <bagassik> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | VERIFIED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
bagas
2009-11-11 07:18:36 UTC
Here is the link to the full log http://slil.ru/28181412/4f65d51f.4afb1248/build1.log You can't mix unstable glibc with stable kde. Use at least kdelibs-4.3.3. *** This bug has been marked as a duplicate of bug 292072 *** but how could a package from the unstable branch to get to the stable? I have also indicated ACCEPT_KEYWORDS="x86" (In reply to comment #3) > but how could a package from the unstable branch to get to the stable? > > I have also indicated ACCEPT_KEYWORDS="x86" > Portage 2.1.6.13 (default/linux/x86/10.0, gcc-4.3.4, glibc-2.11-r0, ^ From your emerge --info. You must have glibc somewhere in /etc/portage or you manually did ACCEPT_KEYWORDS="~x86" emerge glibc at some point. Either way, your glibc is unstable and was added to portage like few days ago. And we know kdelibs-4.3.1 is broken with it, it won't be fixed. KDE 4.3.3 will go stable end of this month, effectively taking care of the problem. Meanwhile, if you want to use kde with that glibc, use the ~arch one. |