>checking the GLIBC_VERSION version... unsupported version 2.21 >configure: error: Valgrind requires glibc version 2.2 - 2.19 Reproducible: Always
Created attachment 406724 [details] build.log
Created attachment 406726 [details] config.log
There is a patch on Linux from Scratch, I have tried applying it via /etc/portage/patches, but it does not work. Here is the patch: http://www.linuxfromscratch.org/blfs/view/svn/general/valgrind.html
This patch works if you patch configure.ac instead of configure, i.e.: --- a/configure.ac 2015-07-14 23:25:50.000000000 +0300 +++ b/configure.ac 2015-07-14 23:32:45.000000000 +0300 @@ -1025,6 +1025,13 @@ DEFAULT_SUPP="glibc-2.34567-NPTL-helgrind.supp ${DEFAULT_SUPP}" DEFAULT_SUPP="glibc-2.X-drd.supp ${DEFAULT_SUPP}" ;; + 2.21) + AC_MSG_RESULT(2.21 family) + AC_DEFINE([GLIBC_2_21], 1, [Define to 1 if you're using glibc 2.21.x]) + DEFAULT_SUPP="glibc-2.X.supp ${DEFAULT_SUPP}" + DEFAULT_SUPP="glibc-2.34567-NPTL-helgrind.supp ${DEFAULT_SUPP}" + DEFAULT_SUPP="glibc-2.X-drd.supp ${DEFAULT_SUPP}" + ;; darwin) AC_MSG_RESULT(Darwin) AC_DEFINE([DARWIN_LIBC], 1, [Define to 1 if you're using Darwin])
I can confirm this error
emerging dev-util/valgrind-3.10.1 doesn't recognize glibc 2.20/2.21 on a newer system, configure fails with: checking the GLIBC_VERSION version... unsupported version 2.21 configure: error: Valgrind requires glibc version 2.2 - 2.19 There's already a patch "valgrind-3.9.0-glibc-2.19.patch" to make valgrind recognize glibc 2.19, and ArchLinux just applied a similar patch to make it also recognize glibc 2.20/2.21: https://projects.archlinux.org/svntogit/packages.git/plain/trunk/valgrind-3.9.0-glibc-2.21.patch?h=packages/valgrind So this issue is very likely get fixed easily.
Just applied the patch, and valgrind seems running smoothly.
This is a repeated ritual with valgrind. Every time a new version of glibc comes out you need to patch configure.ac. I added epatch_user a while back so users could apply their own patch without waiting for me to get around to it. Just look in the $FILESDIR for a similar patch and modify it. Anyhow 3.10.1 should now build against glibc-2.21. I added the patch to the stable ebuild without revbump. Reopen this bug if it doesn't work for some reason.
Created attachment 428312 [details] dev-util:valgrind-3.10.1:20160315-142723.log.gz Hello Anthony, (In reply to Anthony Basile from comment #8) > Anyhow 3.10.1 should now build against glibc-2.21. I added the patch to the > stable ebuild without revbump. Reopen this bug if it doesn't work for some > reason. The current stable version 3.10.1 doesn't work with sys-libs/glibc in 2.22 branch (the version 2.22-r2 is installed on my system): checking the GLIBC_VERSION version... unsupported version 2.22 configure: error: Valgrind requires glibc version 2.2 - 2.19 Thanks for support.
Sorry for the noise, I forgot to mention the currently unstable version (~amd64) 3.11.0 doesn't have this problem (but others, unfortunately… but not related to this bug report).
