Support for the ARM 64 bit CPU architecture (aarch64) was introduced in autoconf 2.69. libnetfilter_conntrack 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/libnetfilter_conntrack/libnetfilter_conntrack-aarch64.patch which updates config.guess and config.sub to recognize aarch64.
I think this package is just confusing, but not broken. It has old autoconf files in /, and newer in build-aux. Your script detects the old ones but they don't appear to be used, actually. I'll test this idea now.
Yeah, I just deleted compile config.guess config.sub depcomp install-sh ltmain.sh missing, did not rerun autoconf and it still builds fine. I'll close it with my update that bumps version/deletes the confusing files.
libnetfilter_conntrack-1.0.3-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/libnetfilter_conntrack-1.0.3-1.fc17
libnetfilter_conntrack-1.0.3-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/libnetfilter_conntrack-1.0.3-1.fc18
Package libnetfilter_conntrack-1.0.3-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libnetfilter_conntrack-1.0.3-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4389/libnetfilter_conntrack-1.0.3-1.fc18 then log in and leave karma (feedback).
libnetfilter_conntrack-1.0.3-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
libnetfilter_conntrack-1.0.3-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.