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 194515 [details] Build log
i doubt this has anything to do with glibc-2.10 considering we're building glibc itself. it wont use the toolchain's glibc headers when building. probably more likely the fortify code from gcc. warning: "memmove" redefined In file included from ../include/bits/string3.h:1, from ../string/string.h:422, from ../include/string.h:49, from bcopy.c:19: ../string/bits/string3.h:55:1: warning: this is the location of the previous definition In file included from bcopy.c:30: ./memmove.c:42: error: expected identifier or '(' before 'void' ./memmove.c:42: error: expected ')' before '(' token In file included from bcopy.c:30: ./memmove.c:46: error: expected identifier or '(' before '{' token
fortify source is disabled now http://sources.gentoo.org/app-emulation/emul-linux-x86-glibc-errno-compat/emul-linux-x86-glibc-errno-compat-2.5.ebuild?r1=1.1&r2=1.2
Hello I'm having the same problem, but I do not understand how you have solved it. Can you detail more? In advance thank you Thomas
