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.
(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.