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 197887 [details] Build log
Created attachment 199875 [details, diff] fixes compile with glibc-2.10.1 this is a quick and easy patch for kdbg. Basically it addresses the issue of things like this: const char *p = ...; char *s = strchr(p, x); /* drops the const! */
I forgot to mention, this patch is for kdb-2.1.1. appears to apply cleanly against 2.1.0 as well.
08 Aug 2009; Samuli Suominen <ssuominen@gentoo.org> kdbg-2.1.1.ebuild, + +files/kdbg-2.1.1-glibc-2.10.patch: + Fix building with GLIBC 2.10+ wrt #277774, thanks to Evan Teran for patch.
