I'm fiddling with QT 3.3.4 and KDE-3.4.0 on an (admittedly modified) LFS svn circa yesterday (nALFS scripted build)...
Everything is peachy up until I get to kdebindings, which craps out with the following error: -: make[2]: Entering directory `/tools/build/kdebindings-3.4.0/python' -: mkdir sip -: mkdir: cannot create directory `sip': File exists -: make[2]: [sipdone] Error 1 (ignored) -: export builddir=`pwd` ; \ -: cd ./sip ; \ -: export QTDIR=/usr/include/ ; \ -: /usr/bin/python configure.py -b /usr/bin -d /usr/lib/python2.4/site-packages -e `echo -I/usr/include/python2.4 | sed s/-I//` -l qt-mt -v /usr/share/sip/ -t "$builddir/sip" INCDIR_QT=/usr/include/qt -: Error: This version of Qt seems to use tmake but the TMAKEPATH environment is -: not set. -: make[2]: *** [sipdone] Error 1 -: make[2]: Leaving directory `/tools/build/kdebindings-3.4.0/python' -: make[1]: *** [all-recursive] Error 1 -: make[1]: Leaving directory `/tools/build/kdebindings-3.4.0' -: make: *** [all] Error 2 Now, according to various mailing lists there may be an issue with QTDIR being set incorrectly, so I've tried setting QTDIR=/usr in python/Makefile.am and re-running aclocal, but then I still get the same error as above, only of course with the QTDIR line changed :) Why is Qt trying to use tmake, anyhow?? QT 3.x uses qmake. tmake isn't even on the system! The core KDE packages built just fine and run slick as butter. One last piece of (possibly relevant) information is that /usr/share/qt/mkspecs/linux-g++/linux-g++ is a broken symlink pointing to the qt build directory. What's with that?? Jeremy -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
