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 926695

Summary: vfrnav: Does not support aarch64 in f19 and rawhide
Product: [Fedora] Fedora Reporter: Dennis Gilmore <dennis>
Component: vfrnavAssignee: Thomas Sailer <t.sailer>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: pbrobinson, t.sailer
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-29 18:02:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 922257    

Description Dennis Gilmore 2013-03-23 16:29:56 UTC 
Support for the ARM 64 bit CPU architecture (aarch64) was introduced in 
autoconf 2.69.  vfrnav 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/vfrnav/vfrnav-aarch64.patch
which updates config.guess and config.sub to recognize aarch64.
Comment 1 Thomas Sailer 2013-04-30 08:00:20 UTC 
(In reply to comment #0)
> Support for the ARM 64 bit CPU architecture (aarch64) was introduced in 
> autoconf 2.69.  vfrnav appears to use an earlier version of 
> autoconf, preventing its being built.  This can be fixed in of three ways
> (In order of preference):

There's a chance of this working now.

vfrnav generally uses the autoconf shipped with active fedora releases. So make sure that the autoconf's in active fedora releases are non-broken, then it should propagate within a few weeks into vfrnav.

Thank you.