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 194122 [details] Build log
Created attachment 197255 [details, diff] tries to bump ebuild to EAPI=2 and renames the function offending glibc210/gcc44
http://blog.flameeyes.eu/2009/07/08/how-_not_-to-fix-glibc-2-10-function-collisions
fixed. thanks for the patch.