On Thursday 08 September 2005 12:54, Andreas Simon wrote: > On Thursday 08 September 2005 03:00, Tom Bruno wrote: > > g++ -c -pipe -fno-strict-aliasing -O2 -Wall -W -D_REENTRANT > > -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_GUI_LIB -DQT_QT3SUPPORT_LIB > > -DQT3_SUPPORT -DQT_SHARED -I/usr/share/qt/mkspecs/default -I. > > -I/usr/include/Qt3Support -I/usr/include/QtGui -I/usr/include/QtCore > > -I/usr/include -I. -I../libs -I"`pg_config --includedir`" > > -I"/usr/include/pqxx" -I. -I. -o patientselect.o patientselect.cpp > > patientselect.cpp: In member function ‘void > > PatientSelect::updateTable()’: patientselect.cpp:183: error: ‘class > > QString’ has no member named ‘toStdString’ > > [...] > > > patientselect.cpp:250: error: ‘fromStdString’ is not a member of > > ‘QString’ patientselect.cpp:257: error: ‘fromStdString’ is not a member > > of ‘QString’ make: *** [patientselect.o] Error 1 > > > > > > QString is included, and as I said, the source does compile. I can't > > tell where it is looking for the QString class at. > > The Qt4 documentation states that QString::toStdString and > QString::fromStdString are "only available if Qt is configured with STL > compabitility enabled." > > Thus I wonder if SUSE Linux' Qt is configured without STL compatibility. If > that's the case maybe you want to post a bug report to bugzilla.novell.com. > I think there speaks nothing against having Qt configured with STL > compatibility.
it is not, using the -no-stl switch. I am not sure, if this makes sense, but a bugreport would make sense :) -- Adrian Schroeter SuSE AG, Maxfeldstr. 5, 90409 Nuernberg, Germany email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
