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 197530 [details] Build log
Created attachment 197536 [details] patch for ps_afm.c to fix the getline shenanigans Made a patch. Not sure if that's all but I think so. Hopefully it works, I'm not entirely proficient with this.
Created attachment 197538 [details] missed a parenthesis.
Created attachment 199632 [details, diff] last update, missed src/ in front of filename. Tried and tested, works. Missed a src/ infront of the filename in previous patches. Inclusion in tree imminent?
(In reply to comment #4) > Created an attachment (id=199632) [edit] > last update, missed src/ in front of filename. > > Tried and tested, works. Missed a src/ infront of the filename in previous > patches. Inclusion in tree imminent? applied, thanks