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 197769 [details] Build log
Is it really that it does fail with glibc-2.10? From the build log and ref [2] of Diegos bug report it seems the error is still because of GCC-4.4.0. I will see to get a fix in next hours.
Likely it's the combination of the two.
Created attachment 198354 [details] Addtional patches needed to compile cleanly with GCC-4.4.0 (and glibc-2.10) Provided patch fixes the remaining problems. Compiles cleanly with it here on x86.
Fixed in portage, thanks to Thomas Beierlein for the patch