guys, couldnt you try to fix the build system to not pass -mfpu=neon if neon is detected, but still include arm_neon.h ... which i assume will enable the manually coded neon paths depending on whether the hw feature is on the host?
if that wasnt tried, please consider to do that before regressing all the NEON enabled boards. note that there is not even a single board without NEON supported officially. So while this should be fixed there shouldn't be a reason to rush things here imo. -- QT on armel is built with NEON by default https://bugs.launchpad.net/bugs/664431 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
