There are a few changes in glibc-2.10 that might make your software fail to build with it, please refer to my blog post [1] if you're not sure what the problem is. And no I don't usually provide emerge --info with these bugs because they are caused by glibc-2.10! Thanks, Diego [1] http://blog.flameeyes.eu/2009/05/24/c-libraries-galore
Created attachment 193954 [details] Build log
kde3 theme... seriously, not fixing
Not to start an argument but (imho) Baghira is one of the best KDE 3 themes ever made and... what's wrong about KDE 3 ? Personally I like QT4 and KDE4, but I still use KDE 3 exclusively, and so do *all* my colleagues at work. Maybe we're conservative but... we're perfectly happy with KDE 3. I think fixing this package to work with the newer glibc would be worth it :-)
KDE3 is bitrotting by the day, and most KDE3 packages that fail to build for whatever reasons will just be removed soon. Among other things, they don't seem to play nice with autoconf 2.64.
I advise anyone wondering in this bug copying the theme to your local overlay *now*, if you want to keep using it.
Created attachment 201245 [details, diff] patch for glibc 2.10 compatibility (In reply to comment #5) > I advise anyone wondering in this bug copying the theme to your local overlay > *now*, if you want to keep using it. And if you add this patch, it will continue to work for a little while longer... (add PATCHES="${FILESDIR}/${P}-glibc210.patch" line to the ebuild itself)
Tested x11-themes/baghira-0.8 with the glibc210.patch and it compiles again. Tested and working great. DON'T REMOVE. Still a great theme for KDE3 users. UNMASK. Compiles and works. STABILIZE. Tested on x86.
Applied the patch in portage... let this be for a while then
