Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#38796 - [qt5-declarative] breaks all 32-bit AMD CPUs

Attached to Project: Arch Linux
Opened by Dave (DaveCode) - Wednesday, 05 February 2014, 07:14 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 10 April 2014, 13:04 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Upstream bug incl. my remarks is

Default Qt5 build flags only work on 32-bit Intel; no 32-bit AMD chip exists that can run SSE2.

Qt devs think it a distro issue, not theirs. Available remedies

1. Build Qt5 sans SSE2 for 32-bit arch (works on Intel and AMD alike).
2. Build -intel and -amd variants of Qt5 for 32-bit (use SSE2 flag on Intel variant only).

Not many apps are ported to Qt5 so not much commotion has been heard. When KDE moves it will be news. But it's easy to solve right now, as not many packages are affected.

Apps broken on 32-bit AMD include cmplayer and luminancehdr for example. The list will grow pending a fix.

Thanks Arch
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Thursday, 10 April 2014, 13:04 GMT
Reason for closing:  Fixed
Additional comments about closing:  qt5 5.2.1-3
Comment by Allan McRae (Allan) - Wednesday, 05 February 2014, 09:58 GMT
Intersting... From the linked bug:
"PS: Arch is known to be completely out-of-compliance with Qt Project recommendations. We've given up working with them."

Comment by Pierre Schmitz (Pierre) - Wednesday, 05 February 2014, 17:32 GMT
We should disable SSE2 on 32bit builds as we do with other apps as well. Still looks like an upstream bug if they enable SSE2 when i686 build flags are used.

@Allan: I am not sure, but this might relate to the QT-project recommending shipping a tool which switches links from QT4 to QT5 etc. bypassing the package management. They seem to have a very odd opinion what distros should or should not do.
Comment by Andrea Scarpino (BaSh) - Wednesday, 05 February 2014, 17:35 GMT
@Pierre, Allan
They do not want qtchooser to use Qt5 by default.