valgrind needs Aarch64 port

[Fathi Boudra]

valgrind needs Aarch64 port

[Dennis (dennis-redhat-bugs)]

Support for the ARM 64 bit CPU architecture (aarch64) was introduced in
autoconf 2.69. valgrind appears to use an earlier version of
autoconf, preventing its being built. This can be fixed in of three ways (In order of preference):

1. Work with upstream to migrate the package to autoconf 2.69.

2. Rerun autoconf or autoreconf in %prep or %build prior to running
configure.

3. Apply the patch at http://ausil.fedorapeople.org/aarch64/valgrind/valgrind-aarch64.patch
which updates config.guess and config.sub to recognize aarch64.

[Jakub (jakub-redhat-bugs)]

That looks pretty much as a useless patch, valgrind would need an aarch64 port first, which is several months of work usually.

[Mark (mark-redhat-bugs)]

I agree with Jakub. This doesn't make any sense unless someone is writing an ARM64 port. I don't know about anybody working on it upstream. Lets close till that happens.

[Riku Voipio (riku-voipio)]

The ARM specific code in valgrind is 95K lines, so Aarch64 work is probable as big job. If someone is requesting this, it is better set up as cards in jira than an linaro-aarch64 bug.

[Fathi Boudra (fboudra)]

for the record: https://bugzilla.redhat.com/show_bug.cgi?id=926688

[Marcin Juszkiewicz (hrw)]

Support landed.

[Pjfloyd (pjfloyd)]

aarch64 support was added to Valgrind getting on for 10 years ago.

Release 3.10.0 (10 September 2014)

* Support for the 64-bit ARM Architecture (AArch64 ARMv8). This port
  is mostly complete, and is usable, but some SIMD instructions are as
  yet unsupported.