Public bug reported: On the armel platform in maveirck we guarantee that no NEON support is hard built in by default into any libs, since we support HW in this release that is not capable of using NEON instructions.
On supported HW like marvell dove (or on the unsupported nvidia tegra2), QT applications all die with SIGILL. Examining the build scripts (mainly configure) reveals that QT does build time detection for NEON capabilities. Since our buildds are NEON capable (but not all our target architectures) the configure options need to be adjusted to not do the build time NEON detection by default. For maverick the -no-neon option needs to be handed through to configure from debian/rules. For natty and later releases runtime detection based on hwcaps needs to be implemented in QT. ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New ** Affects: qt4-x11 (Ubuntu Maverick) Importance: High Status: New ** Affects: qt4-x11 (Ubuntu Natty) Importance: Undecided Status: New ** Tags: armel ** Also affects: qt4-x11 (Ubuntu Maverick) Importance: Undecided Status: New ** Also affects: qt4-x11 (Ubuntu Natty) Importance: Undecided Status: New ** Changed in: qt4-x11 (Ubuntu Maverick) Milestone: None => maverick-updates ** Tags added: armel ** Changed in: qt4-x11 (Ubuntu Maverick) Importance: Undecided => High -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs