qt-4.3.0 says redefinition of 'bool QTest::qCompare(const T1&, const T2&, const char*, const char*, const char*, int) [with T1 = double, T2 = double]. Reproducible: Always Steps to Reproduce: 1. Install gentoo on any arm device (for example PDA) 2. emerge qt 3. Wait a few hours. Actual Results: error: redefinition of 'bool QTest::qCompare(const T1&, const T2&, const char*, const char*, const char*, int) [with T1 = double, T2 = double]' Expected Results: It should compile fine and then it should just work. http://svn.debian.org/wsvn/pkg-kde/branches/kde4/packages/qt4-x11/debian/patches/30_arm_ftbfs_fixes.dpatch?op=file&rev=0&sc=0 http://svn.debian.org/wsvn/pkg-kde/branches/kde4/packages/qt4-x11/debian/patches/31_arm_eabi_fix.dpatch?op=file&rev=0&sc=0 this 2 patches required (2-nd for similar bug but with arm-eabi)
Created attachment 125639 [details, diff] patch from debian's svn.
Created attachment 125641 [details, diff] 2-nd patch from debian's svn
Created attachment 125642 [details] qt-4-3.0.ebuild
Comment on attachment 125642 [details] qt-4-3.0.ebuild Fixed ebuild.
Kindly review https://bugs.gentoo.org/page.cgi?id=fields.html#bug_severity; qt is not keyworded for arm at all.
Created attachment 125644 [details] qt-4.3.0.ebuild A bit modified ebuild
can you confirm if this is fixed in Qt-4.3.1, which is now available and in portage?
This bug - yes, but new introduced: generators/unix.unixmake2.cpp: In member function `void UnixMakefileGenerator::writeMakeParts(QTextStream&)`: generators/unix/unixmake2.cpp:107: internal compiler error: Segmentation fault Maybe it is g++'s bug (bug is reproducable with gcc 4.1.2 from protage and custom-build 4.2.1)
ICE isn't the fault of this package, it's the fault of the compiler or your system being too taxed for resources during teh compilation.
it is 64MB Ram and 2GB of Swap. Dmesg doesn't report anything about low memory. And, by the way, I've compiled qt-4.3.0 with attached patches on same environment. I'll do some more tests, but it looks like bug...
I'll tell in around 3 days if the bug is fixed. Qt needs either more ram (or distcc), or -Os instead of -O2 to compile.
And whats the result? :)
(In reply to comment #12) > And whats the result? :) > actual result was that qt-4.4.{0,1} compiles fine =) i'll try to build qt-4.4.2 natively on iwmmxt with eabi (pxa270 machine hx4700)
I keyworded qt-4.5.0, so this shouldn't be an issue anymore.