FWIW the mass-filed "foo: Does not support aarch64" bugs to update config.{guess.sub} in individual packages could/should be closed now, as this is done automatically from %configure macro now (see bug 951442)

(In reply to comment #1)
> FWIW the mass-filed "foo: Does not support aarch64" bugs to update
> config.{guess.sub} in individual packages could/should be closed now, as
> this is done automatically from %configure macro now (see bug 951442)

Seconded.  But, Jon Masters [1] correctly pointed out that the %configure is not
present in all packages relevant to this tracker - there is also needed to
update status for bugs which do not use %configure somehow.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=951442#c14

as pointed out in this thread : 
https://lists.fedoraproject.org/pipermail/devel/2013-June/184098.html 

The better solution is:   
  * Added: BuildRequires: autoconf, automake, libtool, pkgconfig
  * In "%prep" added: autoreconf --install --force 
( from 
https://lists.fedoraproject.org/pipermail/devel/2013-June/184111.html )

(In reply to Pavel Raiskup from comment #2)
> (In reply to comment #1)
> > FWIW the mass-filed "foo: Does not support aarch64" bugs to update
> > config.{guess.sub} in individual packages could/should be closed now, as
> > this is done automatically from %configure macro now (see bug 951442)
> 
> Seconded.  But, Jon Masters [1] correctly pointed out that the %configure is
> not
> present in all packages relevant to this tracker - there is also needed to
> update status for bugs which do not use %configure somehow.
> 
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=951442#c14

So when will the wrongly opened bugs be closed?

Adding Tracking, FutureFeature keywords to avoid rawhide rebase.

*** Bug 978473 has been marked as a duplicate of this bug. ***

Should be linked against ARMTracker https://bugzilla.redhat.com/show_bug.cgi?id=245418 or F-ExcludeArch-ARM https://bugzilla.redhat.com/show_bug.cgi?id=485251