Support for the ARM 64 bit CPU architecture (aarch64) was introduced in autoconf 2.69. nano 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/nano/nano-aarch64.patch which updates config.guess and config.sub to recognize aarch64.
(In reply to comment #0) > 1. Work with upstream to migrate the package to autoconf 2.69. This already the case for the latest upstream release, which is now in rawhide. > 2. Rerun autoconf or autoreconf in %prep or %build prior to running > configure. I will do this for the f19 branch.
fixed in nano-2.3.2-2.fc20
nano-2.3.1-7.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/nano-2.3.1-7.fc19
Package nano-2.3.1-7.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing nano-2.3.1-7.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4905/nano-2.3.1-7.fc19 then log in and leave karma (feedback).
nano-2.3.1-7.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.