Support for the ARM 64 bit CPU architecture (aarch64) was introduced in autoconf 2.69. hmmer 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/hmmer/hmmer-aarch64.patch which updates config.guess and config.sub to recognize aarch64.
Hi, (In reply to comment #0) > 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/hmmer/hmmer-aarch64.patch > which updates config.guess and config.sub to recognize aarch64. I went with option 2 and pushed a change in rawhide git. Can you please test if it fixes the build failure you observed on aarch64 ? I just attempted a scratch build for arch aarch64, but it fails by saying that there is no such arch available: alpha_chris: fedpkg scratch-build --arches aarch64 Building hmmer-3.0-7.fc20 for rawhide Created task: 5168086 Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=5168086 Watching tasks (this may be safely interrupted)... 5168086 build (rawhide, /hmmer:0f9bdfd1e694b46ad5f6ab94d00c403c207bd1da): free 5168086 build (rawhide, /hmmer:0f9bdfd1e694b46ad5f6ab94d00c403c207bd1da): free -> open (buildvm-25.phx2.fedoraproject.org) 5168087 buildSRPMFromSCM (/hmmer:0f9bdfd1e694b46ad5f6ab94d00c403c207bd1da): open (buildvm-09.phx2.fedoraproject.org) 5168087 buildSRPMFromSCM (/hmmer:0f9bdfd1e694b46ad5f6ab94d00c403c207bd1da): open (buildvm-09.phx2.fedoraproject.org) -> closed 0 free 1 open 1 done 0 failed 5168086 build (rawhide, /hmmer:0f9bdfd1e694b46ad5f6ab94d00c403c207bd1da): open (buildvm-25.phx2.fedoraproject.org) -> FAILED: BuildError: No matching arches were found 0 free 0 open 1 done 1 failed 5168086 build (rawhide, /hmmer:0f9bdfd1e694b46ad5f6ab94d00c403c207bd1da) failed
there is no aarch64 hardware, we are going through the initial bootstrap of the new arch using simulators.