valgrind:fix bug 1129 for supporting kernel 3.0
Hi Saul,
This pull request adds 3.0 kernel supports in valgrind's configure.in, which fixed bug 1129. Please help to review and pull.
[YOCTO #1129]
Thanks,
Tong
The following changes since commit 19252e0592c59ed0fb06ca510d11e564518f746d:
Nitin A Kamble (1):
x86 tune inc files: add x32 abi tune parameters
are available in the git repository at:
git://git.pokylinux.org/poky-contrib tlin100/bug1129
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=tlin100/bug1129
Lin Tong (1):
valgrind: supporting Linux kernel 3.0
.../valgrind-3.6.1/fix_3.0_kernel_support.patch | 26 ++++++++++++++++++++ meta/recipes-devtools/valgrind/valgrind_3.6.1.bb | 3 +- 2 files changed, 28 insertions(+), 1 deletions(-) create mode 100644 meta/recipes-devtools/valgrind/valgrind-3.6.1/fix_3.0_kernel_support.patch
PATCH 1/1 valgrind: supporting Linux kernel 3.0
The old valgrind package do not support for Linux kernel 3.0, only for kernel 2.6 and 2.4 Now adding the new configuration to the configure.in file to support Linux kernel 3.0
This commit fixes the problem in valgrind[YOCTO #1129]
--- .../valgrind-3.6.1/fix_3.0_kernel_support.patch | 26 ++++++++++++++++++++ meta/recipes-devtools/valgrind/valgrind_3.6.1.bb | 3 +- 2 files changed, 28 insertions(+), 1 deletions(-) create mode 100644 meta/recipes-devtools/valgrind/valgrind-3.6.1/fix_3.0_kernel_support.patch
meta/recipes-devtools/valgrind/valgrind-3.6.1/fix_3.0_kernel_support.patch new file +26 -0
@@ -0,0 +1,26 @@ +valgrind:Add "3.0.*" statement to the "case" statement for supporting the kernel 3.0.* . + +Signed-off-by: Tong Lin <[email protected]> + +Upstream-Status: Pending + +diff --git a/configure.in b/configure.in +index 3878619..f09720e 100644 +--- a/configure.in ++++ b/configure.in +@@ -229,10 +229,13 @@ case "${host_os}" in + AC_MSG_RESULT([2.4 family (${kernel})]) + AC_DEFINE([KERNEL_2_4], 1, [Define to 1 if you're using Linux 2.4.x]) + ;; +- ++ 3.0.*) ++ AC_MSG_RESULT([3.0 family (${kernel})]) ++ AC_DEFINE([KERNEL_3_0], 1, [Define to 1 if you're using Linux 3.0.x]) ++ ;; + *) + AC_MSG_RESULT([unsupported (${kernel})]) +- AC_MSG_ERROR([Valgrind works on kernels 2.4, 2.6]) ++ AC_MSG_ERROR([Valgrind works on kernels 2.4, 2.6, 3.0]) + ;; + esac +
meta/recipes-devtools/valgrind/valgrind_3.6.1.bb +2 -1
@@ -7,10 +7,11 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=c46082167a314d785d012a244748d803 \ file://include/valgrind.h;beginline=1;endline=56;md5=13a71cedba99112334d8596162aec37e \ file://COPYING.DOCS;md5=8fdeb5abdb235a08e76835f8f3260215" DEPENDS = "virtual/libx11" -PR = "r0" +PR = "r1" SRC_URI = "http://www.valgrind.org/downloads/valgrind-${PV}.tar.bz2 \ file://fix_issue_caused_by_ccache.patch \ + file://fix_3.0_kernel_support.patch \ file://fixed-perl-path.patch" SRC_URI[md5sum] = "2c3aa122498baecc9d69194057ca88f5"
Signature · 1 line
1.7.0.4
Re: [PATCH 1/1] valgrind: supporting Linux kernel 3.0
Op 9 aug. 2011, om 10:30 heeft Lin Tong het volgende geschreven:
Quoted 26 lines
The old valgrind package do not support for Linux kernel 3.0, only for kernel 2.6 and 2.4 Now adding the new configuration to the configure.in file to support Linux kernel 3.0
This commit fixes the problem in valgrind[YOCTO #1129]
Signed-off-by Lin Tong <[email protected]>---
.../valgrind-3.6.1/fix_3.0_kernel_support.patch| 26 ++++++++++++++++++++
meta/recipes-devtools/valgrind/valgrind_3.6.1.bb | 3 +-2 files changed, 28 insertions(+), 1 deletions(-)create mode 100644
meta/recipes-devtools/valgrind/valgrind-3.6.1/fix_3.0_kernel_support.patchmeta/recipes-devtools/valgrind/valgrind-3.6.1/fix_3.0_kernel_support.patch new file +8
-0@@ -0,0 +1,26 @@ +valgrind:Add "3.0.*" statement to the "case" statement for supporting the kernel 3.0.* . + +Signed-off-by: Tong Lin <[email protected]> + +Upstream-Status: Pending + +diff --git a/configure.in b/configure.in +index 3878619..f09720e 100644
meta/recipes-devtools/valgrind/valgrind-3.6.1/fix_3.0_kernel_support.patch line 18
Quoted 10 lines
meta/recipes-devtools/valgrind/valgrind-3.6.1/fix_3.0_kernel_support.patch new file +10
-0+--- a/configure.in ++++ b/configure.in +@@ -229,10 +229,13 @@ case "${host_os}" in + AC_MSG_RESULT([2.4 family (${kernel})]) + AC_DEFINE([KERNEL_2_4], 1, [Define to 1 if you're using Linux 2.4.x]) + ;; +- ++ 3.0.*) ++ AC_MSG_RESULT([3.0 family (${kernel})]) ++ AC_DEFINE([KERNEL_3_0], 1, [Define to 1 if you're using Linux 3.0.x])
And that will break with 3.1.x, 3.2.x, etc. 3.1.x is approx 8 weeks away.