On 22.05.06 10:50:45, Patrick Stinson wrote: > qt-4.1.3 configured with "-release -qt-gif -no-qt3support" > > c++ -c -pipe -fPIC -Os -Wall -W -DQT_NO_DEBUG -DQT_GUI_LIB > -DQT_CORE_LIB -I. > -I/System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3 > -I/usr/local/Trolltech/Qt-4.1.3/mkspecs/default > -I/usr/local/Trolltech/Qt-4.1.3/include > -I/usr/local/Trolltech/Qt-4.1.3/lib/QtGui.framework/Headers > -I/usr/local/Trolltech/Qt-4.1.3/lib/QtCore.framework/Headers > -F/usr/local/Trolltech/Qt-4.1.3/lib -o sipQtGuipart0.o > sipQtGuipart0.cpp > c++ -headerpad_max_install_names -bundle -F/System/Library/Frameworks > -framework Python -o QtGui.so sipQtGuipart0.o > -F/usr/local/Trolltech/Qt-4.1.3/lib > -L/usr/local/Trolltech/Qt-4.1.3/lib -framework QtGui -framework QtCore > /usr/bin/ld: Undefined symbols: > QPrinter::setPrintRange(QPrinter::PrintRange) > QPrinter::printRange() const > collect2: ld returned 1 exit status > make[1]: *** [QtGui.so] Error 1 > make: *** [all] Error 2 > > I've found this to be a problem with qt, as a simple test.cpp proved. > compiling qt-4.1.3 with qt3 support seemed to work.
I already sent a message about this to this list, Phil didn't react at all. I also filed an issue with TT, they said it might be fixed Qt4.2. Andreas -- It is so very hard to be an on-your-own-take-care-of-yourself-because-there-is-no-one-else-to-do-it-for-you grown-up. _______________________________________________ PyKDE mailing list [email protected] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
