Bug 947440 - 3.8.1-12 breaks building on ARM
Summary: 3.8.1-12 breaks building on ARM
Alias: None
Product: Fedora
Classification: Fedora
Component: valgrind
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
Reported: 2013-04-02 12:32 UTC by Peter Robinson
Modified: 2013-04-20 19:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-04-20 19:13:51 UTC

Attachments (Terms of Use)

Description Peter Robinson 2013-04-02 12:32:22 UTC
3.8.1-12 breaks building on ARM for some reason, all builds up to 3.8.1-11 built fine so I'm not sure what's changed to break the CPU detection

* Wed Mar 20 2013 Mark Wielaard <mjw@redhat.com> 3.8.1-12
- Add valgrind-3.8.1-text-segment.patch 
- Don't undefine _missing_build_ids_terminate_build. 

checking for a supported version of gcc... ok (4.8.0)
checking build system type... armv7hl-redhat-linux-gnu
checking host system type... armv7hl-redhat-linux-gnu
checking for a supported CPU... no (armv7hl)
configure: error: Unsupported host architecture. Sorry


Comment 1 Mark Wielaard 2013-04-02 12:45:03 UTC
Sorry about that. That change also regenerated the configure script and had the following hunk in it:

+@@ -5328,7 +5328,7 @@
+         ARCH_MAX="s390x"
+         ;;
+-     armv[57]*)
++     armv57*)
+       { $as_echo "$as_me:${as_lineno-$LINENO}: result: ok (${host_cpu})" >&5
+ $as_echo "ok (${host_cpu})" >&6; }
+       ARCH_MAX="arm"

That seems pretty wrong. Need to track down where that came from.

Comment 2 Jakub Jelinek 2013-04-02 12:48:11 UTC
Maybe m4 ate it?  Missing changequote around it to prevent [] being eaten?

Comment 3 Fedora Update System 2013-04-02 20:08:33 UTC
valgrind-3.8.1-13.fc19 has been submitted as an update for Fedora 19.

Comment 4 Fedora Update System 2013-04-20 19:13:55 UTC
valgrind-3.8.1-13.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.