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.
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.