Created attachment 373950 [details] config.log > checking the GLIBC_VERSION version... unsupported version 2.19 > configure: error: Valgrind requires glibc version 2.2 - 2.17 [IP-] [ ] sys-libs/glibc-2.19:2.2 Did not try with glibc 2.18, but suspect equally broken. ( somebody commented as such on #458326 ). > Portage 2.2.10 (default/linux/amd64/13.0, gcc-4.8.2, glibc-2.19, 3.13.5-gentoo x86_64) > Timestamp of tree: Sun, 30 Mar 2014 14:00:01 +0000 I considered making this a blocker on #486268 , but I didn't due to not testing 5.18 directly.
Created attachment 373952 [details] emerge --info
A possible patch : https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20140217/1196240.html or : https://github.com/archlinuxarm/PKGBUILDs/blob/master/extra/valgrind/valgrind-3.9.0-glibc-2.19.patch or : http://patchwork.openembedded.org/patch/66865/
compiles fine with: https://github.com/archlinuxarm/PKGBUILDs/blob/master/extra/valgrind/valgrind-3.9.0-glibc-2.19.patch
Created attachment 374988 [details, diff] valgrind glibc-2.19 patch
Created attachment 374990 [details] valgrind-3.9.0.ebuild
Committed without a rev bump. Please test.
Confirmation that it works for me with this patch applied. Thanks.
i am on AMD64 stable ... i get 3.8.1 by default, which exposes the same problem. 3.9.0 emerges fine after keywording it ... please stabilize