Op 9 aug. 2011, om 10:30 heeft Lin Tong het volgende geschreven:
> 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 <tong....@intel.com>
> ---
> .../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
>
> diff --git
> a/meta/recipes-devtools/valgrind/valgrind-3.6.1/fix_3.0_kernel_support.patch
> b/meta/recipes-devtools/valgrind/valgrind-3.6.1/fix_3.0_kernel_support.patch
> new file mode 100644
> index 0000000..54fc481
> --- /dev/null
> +++
> b/meta/recipes-devtools/valgrind/valgrind-3.6.1/fix_3.0_kernel_support.patch
> @@ -0,0 +1,26 @@
> +valgrind:Add "3.0.*" statement to the "case" statement for supporting the
> kernel 3.0.* .
> +
> +Signed-off-by: Tong Lin <tong....@intel.com>
> +
> +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])
And that will break with 3.1.x, 3.2.x, etc. 3.1.x is approx 8 weeks away.
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
