Support for the ARM 64 bit CPU architecture (aarch64) was introduced in autoconf 2.69. ardour 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/ardour/ardour-aarch64.patch which updates config.guess and config.sub to recognize aarch64.
Hi, just out of curiousity, what kind of ARM machine, do you think, would provide a use case to run ardour?
Hi, (In reply to comment #1) > Hi, just out of curiousity, what kind of ARM machine, do you think, would > provide a use case to run ardour? TBH that does not really matter, in Fedora we simply want all packages to build on all atchs. Even so the new A15 based Samsung chromebooks should be more then capable of running ardour and certainly future 64 bit arm machines will be capable too. Regards, Hans
ardour-2.8.16-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/ardour-2.8.16-3.fc19
Package ardour-2.8.16-3.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 ardour-2.8.16-3.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-7888/ardour-2.8.16-3.fc19 then log in and leave karma (feedback).
ardour-2.8.16-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.