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 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
Created attachment 197253 [details] Build log
Fixed *this* issue, but GCC 4.4.1 dies with "Internal compiler" error anyway with this package, unless you enforce -O0 or -g instead of -O2... After that there's even more problems. Anyway, this bug is fixed, if you care enough -> new issues -> new bugs