This may be the correct fix that does not require disabling neon: https://git.libav.org/?p=libav.git;a=commitdiff;h=34fb994d9340313b0d247899a4a7a97cc010df92;hp=e780c3daafe0588e035e752c771ebfcd2201746a
Again, testing appreciated -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1323144 Title: FTBFS with NEON on arm64 Status in “libav” package in Ubuntu: Triaged Bug description: The latest version of libav in utopic-proposed/unstable (6:10.1-1) fails to build from source with NEON enabled. The relevant build log is here: https://launchpadlibrarian.net/176152432/buildlog_ubuntu- utopic-arm64.libav_6%3A10.1-1_FAILEDTOBUILD.txt.gz One suggestion on IRC was to simply disable NEON on arm64 for libav, but there might be another possible approach to fixing this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1323144/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
