Support for the ARM 64 bit CPU architecture (aarch64) was introduced in autoconf 2.69. scanssh 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/scanssh/scanssh-aarch64.patch which updates config.guess and config.sub to recognize aarch64.
Tried to contact upstream. Let's see...
Message from upstream (Kenneth Pronovici): This is done. Get the latest tarball here: http://software.cedar-solutions.com/ftp/software/banner-1.3.3.tar.gz I can't test that the program will build properly for ARM 64 systems, but at least I see the changes I would expect in the autoconf files (i.e. the same ones in the patch attached to your bug report).
Ooops. Wrong bug. for Comment 2.
Regarding scanssh. Upstream decided to retire maintenance of the software. Therefore I've taken over the software (https://github.com/ofalk/scanssh); Niels Provos was OK with this - of course.
scanssh-2.1.1-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/scanssh-2.1.1-1.fc19
Package scanssh-2.1.1-1.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 scanssh-2.1.1-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4912/scanssh-2.1.1-1.fc19 then log in and leave karma (feedback).
scanssh-2.1.1-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.