Summary: | dev-util/valgrind-3.9.0 does not work with glibc 2.19 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kent Fredric (IRC: kent\n) (RETIRED) <kentnl> |
Component: | [OLD] Development | Assignee: | Anthony Basile <blueness> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | const, groepaz, nictki, remi, rodolphe.rocca, ulm, vityokster |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
config.log
emerge --info valgrind glibc-2.19 patch valgrind-3.9.0.ebuild |
Description
Kent Fredric (IRC: kent\n) (RETIRED)
![]() 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 |