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 926075

Summary: lingot: Does not support aarch64 in f19 and rawhide
Product: [Fedora] Fedora Reporter: Dennis Gilmore <dennis>
Component: lingotAssignee: Karel Volný <kvolny>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dennis, kvolny, sanjay.ankur
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: 2014-01-31 16:36:24 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 15:24:12 UTC
Support for the ARM 64 bit CPU architecture (aarch64) was introduced in 
autoconf 2.69.  lingot 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/lingot/lingot-aarch64.patch
which updates config.guess and config.sub to recognize aarch64.

Comment 1 Ankur Sinha (FranciscoD) 2013-03-24 01:49:57 UTC
Cannot be built due to this bug: 

https://bugzilla.redhat.com/show_bug.cgi?id=924938

Pushed to SCM. Will push a build as soon as the bug is fixed.

Ankur

Comment 2 Karel Volný 2014-01-31 16:09:39 UTC
ping, if I recall correctly, ARM support has been somehow hacked at buildsys level, is this bug still relevant?

the next upstream version is going to use 2.69 - at least

http://hg.savannah.gnu.org/hgweb/lingot/file/7ed4f5d21d15/configure

says

# Generated by GNU Autoconf 2.69.


... but I can't guess when it will be released

would that be okay to switch this to closed/upstream?

Comment 3 Karel Volný 2014-01-31 16:36:24 UTC
(In reply to Karel Volný from comment #2)
> ping, if I recall correctly, ARM support has been somehow hacked at buildsys
> level, is this bug still relevant?

ah, I could answer my own question by reading bug #922257 #c1

so, this is no longer an issue