Compilation fails with qt 4.7

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install qt 4.7
2. Compile

What is the expected output? What do you see instead?

g++ -c -pipe -march=i686 -mtune=generic -O2 -pipe -Wall -W -D_REENTRANT 
-DQT_NO_DEBUG -DQT_SCRIPT_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB 
-DQT_SHARED -I/usr/share/qt/mkspecs/linux-g++ -I. -I/usr/include/QtCore 
-I/usr/include/QtNetwork -I/usr/include/QtGui -I/usr/include/QtScript 
-I/usr/include -Iinc -Iinc/models -Iinc/grid_view -Iinc/docks -Iui 
-Ithirdparty/qtcolorpicker-2.6 -Ibin/release -Ibin/release -o 
bin/release/memorylayout.o src/memorylayout.cpp
src/memorylayout.cpp: In constructor ‘MemoryLayout::MemoryLayout(const 
QString&)’:
src/memorylayout.cpp:12:22: error: call of overloaded ‘QString(int)’ is 
ambiguous
/usr/include/QtCore/qstring.h:428:43: note: candidates are: 
QString::QString(const QByteArray&)
/usr/include/QtCore/qstring.h:426:43: note: QString::QString(const char*)
/usr/include/QtCore/qstring.h:727:8: note: QString::QString(const QString&)
/usr/include/QtCore/qstring.h:106:5: note: QString::QString(QChar)
/usr/include/QtCore/qstring.h:105:14: note: QString::QString(const QChar*)
make: *** [bin/release/memorylayout.o] Error 1
Aborting...
error: Build failed

What version of the product are you using? On what operating system?

dwarftherapist 0.6.0, Archlinux

Fix is attached.

Original issue reported on code.google.com by Jakob.Gr...@gmail.com on 30 Sep 2010 at 1:40

Attachments:

• dwarftherapist_qstring.patch

[GoogleCodeExporter]

Original comment by treyst...@gmail.com on 13 Oct 2010 at 4:41

[GoogleCodeExporter]

Original comment by ehler...@gmail.com on 13 Nov 2010 at 7:34

• Changed state: Accepted

[GoogleCodeExporter]

Compilation is successfull since 
http://code.google.com/p/dwarftherapist/source/detail?spec=svnca851122a0c0963e40
71a68217635d0dd5be2df8&r=fba5aa43a720a967afa7a5fc5e1da29b36db2d31

Original comment by Jakob.Gr...@gmail.com on 13 Nov 2010 at 8:38

[GoogleCodeExporter]

I think the QString::null is a better fix however, so going to do some testing 
then mark this as resolved.

Original comment by ehler...@gmail.com on 13 Nov 2010 at 4:40

[GoogleCodeExporter]

Original comment by ehler...@gmail.com on 13 Nov 2010 at 6:18

• Changed state: Fixed