valgrind-2.0.0.ebuild includes a patch from the previous valgrind prerelease which enables it to build on 2.6 series kernels. This patch is no longer needed in the 2.0.0 version, and patching fails preventing the emerge from completing. Commenting out the patch produced a fully-working valgrind on my 2.6 system. Thanks! Steven Robertson
I agree. the patch is not needed. Without the patch entry in the .ebuild file, it emerges correctly, and runs. The patch causes this: - >>> emerge (3 of 4) dev-util/valgrind-2.0.0 to / >>> md5 src_uri ;-) valgrind-2.0.0.tar.bz2 >>> Unpacking source... >>> Unpacking valgrind-2.0.0.tar.bz2 to /var/tmp/portage/valgrind-2.0.0/work * Applying valgrind-configure.in-2.6.diff... * Failed Patch: valgrind-configure.in-2.6.diff! * * Include in your bugreport the contents of: * * /var/tmp/portage/valgrind-2.0.0/temp/valgrind-configure.in-2.6.diff-20517.out !!! ERROR: dev-util/valgrind-2.0.0 failed. !!! Function epatch, Line 354, Exitcode 0 !!! Failed Patch: valgrind-configure.in-2.6.diff!
Confirmed. After commenting out the patch, emerged fine on my 2.6.0-test9 system...
Valgrind still needs patching to make it work with kernel-2.6. See bug report #32966.
I dont get it, dont developers test their ebuilds before integrating them with the tree? I mean, just update the version and fingers crossed?
The problem in bug #32966 is not present on for all people running 2.6. That bug is a build problem and the thought is (at least by me ;) that it might be due to nptl. The patch in this case is for the configure script, and is not needed becasue the config.in already contains the check for 2.6.
this was fixed yesterday.
