Summary: | x11-libs/qt-gui-4.7.2 fails to compile on AMD E-350 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jürgen Pierau <gentoo-bugs> |
Component: | [OLD] Library | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Log of failed build |
Description
Jürgen Pierau
2011-05-11 17:45:52 UTC
Removing -mno-3dnow from CFLAGS allows compilation, but I'm not sure I want to run this. Please attach the entire build log. Created attachment 273075 [details]
Log of failed build
FYI gcc 4.4.5's -march=native seems not not correctly identify the instruction sets. My first Gentoo installation on this system failed to survive the bootup to the default runlevel with some unknown instruction exceptions (I think it was in code that wanted to test different memcopy methods), hence the -mno-3dnow. There is a closed QT bug that fits the problem: http://bugreports.qt.nokia.com/browse/QTBUG-18688 It seems compiling QT with 3dnow is not a problem, because QT uses runtime cpu detection (let's assume for the moment that this detection algorithm is better than that of gcc). However, other software is not so - enlightened. Some way of deliberately choosing not to use 3dnow in qt-gui without removing -mno-3dnow for all packages would be greatly appreciated. I understand that the reported bug is that features of your processor is incorrectly detected, and so it is a bug from QT, may be not exactly that of http://bugreports.qt.nokia.com/browse/QTBUG-18688, that seems to be a problem on the ebuild. The root cause is probably bug #336618 Indeed, your safest option is to keep -mno-3dnow in your C(XX)FLAGS, at least until gcc's -march=native gets fixed for your CPU. On the other hand, qt4-build.eclass doesn't pass user's CFLAGS to configure, so we have a bug on our side too, which is #336618. *** This bug has been marked as a duplicate of bug 336618 *** |