Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 213411

Summary: x11-libs/qt-4.3.x has aliasing problems
Product: Gentoo Linux Reporter: Hanno Zysik (geki) <h.mth>
Component: New packagesAssignee: Qt Bug Alias <qt>
Status: RESOLVED FIXED    
Severity: normal CC: gnu_andrew, loki_val, main.haarp
Priority: High    
Version: 2007.0   
Hardware: All   
OS: Linux   
URL: http://cvs.fedoraproject.org/viewcvs/*checkout*/devel/qt/qt-x11-opensource-src-4.3.4-aliasing.patch
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on:    
Bug Blocks: 214218    

Description Hanno Zysik (geki) 2008-03-14 17:06:43 UTC
The Qt library version 4.3.x has problems with aliasing.
These should be fixed in 4.4.

Some gcc versions with optimization '-O2' or '-fstrict-aliasing' compile Qt but throw segmentation faults at runtime.

See my mailing list thread at Qt-interest:
http://lists.trolltech.com/qt-interest/2008-03/thread00368-0.html
(Message 6 and onwards get interesting.)

One issue is fixed with the patch from fedora on URL. But on f.g.o and b.g.o I see Qt segfaulting other way, the QApplication constructor.

I recommend to add 'append-flags -fno-strict-aliasing' in src_compile before configure is called.

References:
https://forums.gentoo.org/viewtopic-t-668006.html
https://forums.gentoo.org/viewtopic-t-492597.html
https://forums.gentoo.org/viewtopic-t-674330.html
https://bugs.gentoo.org/192954
Comment 1 Ingmar Vanhassel (RETIRED) gentoo-dev 2008-03-19 04:30:58 UTC
Fixed in qt-4.3.4-r1, thanks for letting us know. :)
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2008-03-22 06:47:32 UTC
*** Bug 214223 has been marked as a duplicate of this bug. ***
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2008-03-22 06:58:32 UTC
Reopen wrt Bug 214218, this thing looks more borked than this...
Comment 4 Mark Loeser (RETIRED) gentoo-dev 2008-05-03 19:01:55 UTC
I don't see a porting problem here :)
Comment 5 Ben de Groot (RETIRED) gentoo-dev 2009-01-03 01:30:39 UTC
*** Bug 241828 has been marked as a duplicate of this bug. ***