Hello After an upgrade of glibc to 2.12.1, valgrind starts reporting many false positives, like the ones noted here: http://www.cygwin.com/ml/libc-alpha/2010-05/msg00024.html or here: http://bugs.archlinux.org/task/19634. Downgrade of glibc is not supported, attempt to reemerge valgrind fails with (end of configure): checking for egrep... /bin/grep -E checking the GLIBC_VERSION version... unsupported version configure: error: Valgrind requires glibc version 2.2 - 2.11 This is kind of unlucky, as it leaves no way to restore valgrind into usable state without complete system reinstall or other risky operations like forced downgrade of glibc (no, I'm not going to try that). May I suggest some kind of block that would stop glibc from upgrading if valgrind is installed? Thanks Reproducible: Always Steps to Reproduce:
emerge --info please
not a bug in glibc
Created attachment 243107 [details] Emerge --info
I do not think it is bug neither in glibc nor in valgrind. Just that glibc does some magic inside and valgrind needs to know about it and it does not yet know this version. With short look trough the internet, they are working on newer valgrind that will know glibc-2.12, but until then, they do not work together, so I think there should be a block in the ebuilds.
valgrind-9999 works fine with glibc-2.12.1 on ~amd64.
http://cvs.fedoraproject.org/viewvc/rpms/valgrind/F-13/valgrind-3.5.0-glibc-2.12.patch
+ 19 Aug 2010; Samuli Suominen <ssuominen@gentoo.org> valgrind-3.5.0.ebuild, + +files/valgrind-3.5.0-glibc-2.12.patch, + +files/valgrind-3.5.0-stat_h.patch: + Fix building with recent glibc wrt #332871 by Michal Vaner.
