Support for the ARM 64 bit CPU architecture (aarch64) was introduced in autoconf 2.69. pam_mount 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/pam_mount/pam_mount-aarch64.patch which updates config.guess and config.sub to recognize aarch64.
Is this still required? I remember that there was some discussion on fedora-devel, that this might not be necessary at all and the bugs would be closed again.
hxtools-20130605-1.fc19,pam_mount-2.13-4.20130707git966c6bea.fc19,libHX-3.15-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/hxtools-20130605-1.fc19,pam_mount-2.13-4.20130707git966c6bea.fc19,libHX-3.15-1.fc19
Package hxtools-20130605-1.fc19, pam_mount-2.13-4.20130707git966c6bea.fc19, libHX-3.15-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 hxtools-20130605-1.fc19 pam_mount-2.13-4.20130707git966c6bea.fc19 libHX-3.15-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-12612/hxtools-20130605-1.fc19,pam_mount-2.13-4.20130707git966c6bea.fc19,libHX-3.15-1.fc19 then log in and leave karma (feedback).
hxtools-20130605-1.fc19, pam_mount-2.13-4.20130707git966c6bea.fc19, libHX-3.15-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.