valgrind needs Aarch64 port
Bug #1236748 reported by
Fathi Boudra
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Linaro AArch64 cross-distro work |
In Progress
|
Medium
|
Unassigned | ||
| valgrind (Fedora) |
Invalid
|
Undecided
|
|||
| valgrind (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
valgrind needs Aarch64 port
Revision history for this message
| Riku Voipio (riku-voipio) wrote | #1 |
| Changed in linaro-aarch64: | |
| status: | New → Triaged |
Revision history for this message
| Fathi Boudra (fboudra) wrote | #2 |
| Changed in valgrind (Ubuntu): | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
Revision history for this message
| Marcin Juszkiewicz (hrw) wrote | #3 |
| Changed in linaro-aarch64: | |
| status: | Triaged → In Progress |
| importance: | Undecided → Medium |
| Changed in valgrind (Fedora): | |
| importance: | Unknown → Undecided |
| status: | Unknown → Invalid |
To post a comment you must log in.
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://
which updates config.guess and config.sub to recognize aarch64.