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. Also make sure to fix it rather than sidestepping the issue [2] and [3]. 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 [2] http://blog.flameeyes.eu/2009/07/02/how-_not_-to-fix-gcc-4-4-bugs [3] http://blog.flameeyes.eu/2009/07/08/how-_not_-to-fix-glibc-2-10-function-collisions
Created attachment 197338 [details] Build log
*** Bug 277468 has been marked as a duplicate of this bug. ***
fixed in cvs http://sources.gentoo.org/sys-libs/uclibc/uclibc-0.9.30.1-r1.ebuild?r1=1.1&r2=1.2 http://sources.gentoo.org/sys-libs/uclibc/uclibc-0.9.30.1.ebuild?r1=1.2&r2=1.3