I found a reference to a similar issue in openal-soft_1:1.16.0-3 from earlier this year.
http://gcc.1065356.n8.nabble.com/distro-test-rebuild-using- GCC-6-td1224722.html#a1226791 It seems the arm headers have changed how configure should detect neon support, and now the build is falsely detecting neon support, even though it's not passing the required -mfpu=neon flag. Given that neon support was not enabled before, I believe the best choice is to disable it via a configure flag. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/1630349 Title: libwebp ftbfs on armhf Status in libwebp package in Ubuntu: In Progress Bug description: https://launchpadlibrarian.net/285964171/buildlog_ubuntu-yakkety- armhf.libwebp_0.5.1-2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/1630349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
