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 202022 [details] Build log
So I started hitting this on ~x86 with seaview-20071113. :(
+ 04 Sep 2009; Samuli Suominen <ssuominen@gentoo.org> + seaview-20071113.ebuild, +files/seaview-20071113-glibc-2.10.patch: + Fix building with GLIBC 2.10+ wrt #282431.