could someone point to the matching commit so we can see the impact ? i dont think we actually care in which way neon is disabled on platforms that dont support it as long as you dont get a SIGILL for all QT apps you try to start. platforms that support NEON will indeed benefit from it but we made a commitment that nothing in the archive is built with NEON for maverick.
it is not acceptable to build QT with NEON statically enabled at build time, i think its a good compromise to use runtime detection if it: a) gets enough testing so we are confident it doesnt add additional regression and b) the patch is small enough -- 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
