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 926610

Summary: tar: Does not support aarch64 in f19 and rawhide
Product: [Fedora] Fedora Reporter: Dennis Gilmore <dennis>
Component: tarAssignee: Pavel Raiskup <praiskup>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: kdudka, ovasik, praiskup
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: 2013-03-27 14:33:05 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:24:31 UTC
Support for the ARM 64 bit CPU architecture (aarch64) was introduced in 
autoconf 2.69.  tar 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/tar/tar-aarch64.patch
which updates config.guess and config.sub to recognize aarch64.

Comment 1 Pavel Raiskup 2013-03-24 16:53:52 UTC
Hi Dennis, I would fix the bug-fill report a little...

(In reply to comment #0)
> Support for the ARM 64 bit CPU architecture (aarch64) was introduced in
> autoconf 2.69.  tar appears to use an earlier version of
> autoconf, preventing its being built.

Actually - there is possible that the package does not use autoconf at all.
Just the './configure' script is generated by older autoconf.

> This can be fixed in of three ways
> (In order of preference):
>
> 1. Work with upstream to migrate the package to autoconf 2.69.

This is done pretty much automatically as the time goes, I hope.  When the
upstream uses the up2date automake the generated config.guess/config.sub is
then distributed in upstream tarball (by running `make dist`).

> 2. Rerun autoconf or autoreconf in %prep or %build prior to running
> configure.

This does not help - you need to run "automake --update-missing --force".  It
is also done during 'autoreconf -v -f -i'.  The '-f -i' options are important
here.  But I'm not sure how much should users be encouraged to use this
command as it may theoretically break the build also (replacing all the
distributed macros with macros in automake).

> 3. Apply the patch at
> http://ausil.fedorapeople.org/aarch64/tar/tar-aarch64.patch
> which updates config.guess and config.sub to recognize aarch64.

I guess this is valid one and imo also innocent.  But I'm unable to test it in
arm distro.  You were creating the patch against automake-1.12 I guess
(automake-1.13 is in rawhide now).

  $ rpm -ql automake | grep config.guess

Pavel

Comment 2 Pavel Raiskup 2013-03-27 14:33:05 UTC
Another possibility would be to copy the updated scripts from automake package.
This is probably not as easy as it look - as there exists multiple automake
packages in Fedora distro ~> so you are unable to copy
/usr/share/automake-*/config.{guess,sub} files.  So the best would be:

 | for file in `rpm -ql automake | grep -e config.guess -e config.sub`; do
 |   cp $file dest_dir
 | done

.. but here you need to have rpm/automake BuildRequires.  So I have used your
approach 3. for tar package (with updated scripts from automake-1.13).

Pavel