Configuration fails for Valgrind 3.10.1 when glibc is 2.23+. This problem doesn't for Valgrind 3.11.0 because configure checks for 2.2*), rather than specific 2.# versions. Therefore: 1) Valgrind-3.10.1 requires a glibc dependency of >=2.2 and <2.23 (needs to be tested, because configure reports 2.2-2.19). 2) Valgrind-3.11.0 and prbably later requires a glibc dependency of >=2.2.
valgrind-3.10.1.ebuild valgrind-3.11.0.ebuild valgrind-3.12.0.ebuild all build for me with sys-libs/glibc-2.23-r3
(In reply to Austin English from comment #1) > valgrind-3.10.1.ebuild > valgrind-3.11.0.ebuild > valgrind-3.12.0.ebuild > > all build for me with sys-libs/glibc-2.23-r3 These three also all build for me with glibc 2.21-r2 in an old chroot I still had. I'm unable to reproduce this at all. @blueness, can you?
(In reply to Austin English from comment #2) > (In reply to Austin English from comment #1) > > valgrind-3.10.1.ebuild > > valgrind-3.11.0.ebuild > > valgrind-3.12.0.ebuild > > > > all build for me with sys-libs/glibc-2.23-r3 > > These three also all build for me with glibc 2.21-r2 in an old chroot I > still had. > > I'm unable to reproduce this at all. @blueness, can you? i finished stabilizing 3.12.0 and dropped 3.10.1 and 3.11.1. we should be all good now.