While it's a good idea to avoid running autoreconf just because two letters that have changed, it makes sense to add the change in the configure.in file, so that autoreconf doesn't break the build.
Signed-off-by: Bernhard Walle <[email protected]> --- ...ure-allow-all-arm-don-t-restrict-to-armv7.patch | 21 +++++++++++++------ 1 files changed, 14 insertions(+), 7 deletions(-) diff --git a/patches/valgrind-3.6.1/0001-configure-allow-all-arm-don-t-restrict-to-armv7.patch b/patches/valgrind-3.6.1/0001-configure-allow-all-arm-don-t-restrict-to-armv7.patch index b2fe6c2..63447b7 100644 --- a/patches/valgrind-3.6.1/0001-configure-allow-all-arm-don-t-restrict-to-armv7.patch +++ b/patches/valgrind-3.6.1/0001-configure-allow-all-arm-don-t-restrict-to-armv7.patch @@ -4,11 +4,10 @@ Subject: [PATCH] configure: allow all arm, don't restrict to armv7 Signed-off-by: Marc Kleine-Budde <[email protected]> --- - configure | 2 +- - 1 files changed, 1 insertions(+), 1 deletions(-) + configure | 2 +- + configure.in | 2 +- + 2 files changed, 2 insertions(+), 2 deletions(-) -diff --git a/configure b/configure -index 699137b..1179122 100755 --- a/configure +++ b/configure @@ -5262,7 +5262,7 @@ $as_echo "ok (${host_cpu})" >&6; } @@ -20,6 +19,14 @@ index 699137b..1179122 100755 { $as_echo "$as_me:${as_lineno-$LINENO}: result: ok (${host_cpu})" >&5 $as_echo "ok (${host_cpu})" >&6; } ARCH_MAX="arm" --- -1.7.4.1 - +--- a/configure.in ++++ b/configure.in +@@ -158,7 +158,7 @@ case "${host_cpu}" in + esac + ;; + +- armv7*) ++ arm*) + AC_MSG_RESULT([ok (${host_cpu})]) + ARCH_MAX="arm" + ;; -- 1.7.6 -- ptxdist mailing list [email protected]
