Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 926558

Summary: sox: Does not support aarch64 in f19 and rawhide
Product: [Fedora] Fedora Reporter: Dennis Gilmore <dennis>
Component: soxAssignee: Frantisek Kluknavsky <fkluknav>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: fkluknav, hhorak, hobbes1069
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 14.4.1-3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-06 15:36:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 922257    

Description Dennis Gilmore 2013-03-23 16:21:08 UTC
Support for the ARM 64 bit CPU architecture (aarch64) was introduced in 
autoconf 2.69.  sox 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/sox/sox-aarch64.patch
which updates config.guess and config.sub to recognize aarch64.

Comment 1 Ulrich Klauer 2013-03-24 08:29:30 UTC
We (upstream) are aware of the issue, because Debian complained earlier. ;-)  We are going to change our release script to make sure that future releases will ship recent config.{sub,guess}. If you need aarch64 support now, you'll have to resort to options 2 or 3 (Debian chose the equivalent of 2).

The root cause is that autoreconf won't overwrite config.{sub,guess} if they are already present, even if those existing copies are outdated. ("autoreconf -i --force" will.)

Comment 2 Frantisek Kluknavsky 2013-04-03 08:04:22 UTC
added autoreconf -vfi