tde-users

users@trinitydesktop.org

18 participants
4167 discussions

kdebase iccconfig.cpp make failure - Round 2

by David C. Rankin

Guys, I have rebuilt all packages just using cmake. tqtinterface, arts and kdelibs all build without a hitch. kdebase continues to fail with the following error: [ 30%] Generating iccconfig_skel.cpp Scanning dependencies of target kcm_iccconfig-module [ 30%] Building CXX object kcontrol/iccconfig/CMakeFiles/kcm_iccconfig-module.dir/iccconfig.cpp.o /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp: In member function ‘void KICCConfig::load(bool)’: /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp:289:38: error: expected type-specifier /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp:289:38: error: cannot convert ‘int*’ to ‘KRandrSimpleAPI*’ in initialization /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp:289:38: error: expected ‘,’ or ‘;’ /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp: In member function ‘virtual void KICCConfig::save()’: /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp:359:37: error: expected type-specifier /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp:359:37: error: cannot convert ‘int*’ to ‘KRandrSimpleAPI*’ in initialization /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp:359:37: error: expected ‘,’ or ‘;’ make[2]: *** [kcontrol/iccconfig/CMakeFiles/kcm_iccconfig-module.dir/iccconfig.cpp.o] Error 1 make[1]: *** [kcontrol/iccconfig/CMakeFiles/kcm_iccconfig-module.dir/all] Error 2 make: *** [all] Error 2 Aborting... Looking at iccconfig.cpp, in' void KICCConfig::load(bool useDefaults )' the line being complained about at 289 is: KRandrSimpleAPI *randrsimple = new KRandrSimpleAPI::KRandrSimpleAPI(); Then again at 359, in 'void KICCConfig::save()' the code is: KRandrSimpleAPI *randrsimple = new KRandrSimpleAPI::KRandrSimpleAPI(); For some reason the build is choking here. I have placed the generated Makefile for iccconfig here: http://www.3111skyline.com/dl/dt/trinity/errors/Makefile-iccconfig If there is anything else that I can send that is helpful, please let me know and I'll provide a link. The build file used was: build() { msg "Setting PATH, CMAKE and Trinity Environment variables" [[ ${PATH%%:*} =~ /opt/qt/bin ]] || export PATH=/opt/qt/bin:$PATH export CMAKE_PREFIX_PATH=/opt/qt export CMAKE_INCLUDE_PATH=/opt/qt/include:/opt/qt/include/tqt export KDEDIR=/opt/trinity export KDEDIRS=/opt/trinity:/usr export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/lib/pkgconfig:/opt/qt/lib/pkgconfig export XDG_CONFIG_DIRS=/etc/xdg:/opt/trinity/etc/xdg:/opt/trinity/etc/xdg export XDG_DATA_DIRS=/usr/share/:/usr/local/share/:/opt/trinity/share:/opt/trinity/share trinity_prefix="/opt/trinity" cd ${srcdir} cmake ../ \ -DCMAKE_INSTALL_PREFIX=${trinity_prefix} \ -DWITH_QT3=ON \ -DBUILD_ALL=ON \ -DCMAKE_SKIP_RPATH=ON make || return 1 } This is pretty much where I'm stuck. What say the gurus on where to look for the answers and how to fix them? -- David C. Rankin, J.D.,P.E.

13 years, 10 months

kdebase make failure if Qt4 installed, QtCore/qfile.h QT_BEGIN_HEADER doesn't name type

by David C. Rankin

[ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/panner.cpp.o [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/kickerSettings.cpp.o In file included from /usr/include/QtCore/QFile:1:0, from /home/david/arch/pkg/tbld/kdebase/src/kicker/libkicker/kickerSettings.cpp:7: /usr/include/QtCore/qfile.h:53:1: error: ‘QT_BEGIN_HEADER’ does not name a type /usr/include/QtCore/qfile.h:62:27: error: expected initializer before ‘:’ token make[2]: *** [kicker/libkicker/CMakeFiles/kickermain-shared.dir/kickerSettings.cpp.o] Error 1 make[1]: *** [kicker/libkicker/CMakeFiles/kickermain-shared.dir/all] Error 2 make: *** [all] Error 2 Aborting... I have 3 x86_64 boxes and 4 i686 boxes I'm building on. Some with kde4, some without. With kde4/Qt4 installed, the kdebase build dies as above. On the boxes without QT4, the build progresses to 30% before the iccconfig.cpp build error. I'm rather stumped.I would like to find a way to tell the kdebase build to NOT EVER-EVER look in /usr/include/QtCore. But so far I haven't found a way to do it. It is clear from the error above, that the qt4 qfile.h is causing the problem. The correct qfile.h is in /opt/qt/include, but for some reason isn't being used: 22:24 providence:~/arch/pkg/tbld/kdebase/kicker/libkicker> pmq -o /usr/include/QtCore/qfile.h /usr/include/QtCore/qfile.h is owned by qt 4.7.1-3 22:24 providence:~/arch/pkg/tbld/kdebase/kicker/libkicker> find /opt/qt/ -name qfile.h /opt/qt/include/qfile.h I try limiting that problem with PATH and kde environment tweaks: build() { msg "Setting PATH, CMAKE and Trinity Environment variables" [[ ${PATH%%:*} =~ /opt/qt/bin ]] || export PATH=/opt/qt/bin:$PATH export CMAKE_PREFIX_PATH=/opt/qt export CMAKE_INCLUDE_PATH=/opt/qt/include:/opt/qt/include/tqt export KDEDIR=/opt/trinity export KDEDIRS=/opt/trinity:/usr export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/lib/pkgconfig:/opt/qt/lib/pkgconfig export XDG_CONFIG_DIRS=/etc/xdg:/opt/trinity/etc/xdg:/opt/trinity/etc/xdg export XDG_DATA_DIRS=/usr/share/:/usr/local/share/:/opt/trinity/share:/opt/trinity/share trinity_prefix="/opt/trinity" cd ${srcdir} cmake ../ \ -DCMAKE_INSTALL_PREFIX=${trinity_prefix} \ -DWITH_QT3=ON \ -DBUILD_ALL=ON \ -DCMAKE_SKIP_RPATH=ON make || return 1 } But even with these variables, the build grabs QtCore regardless. Are there any other cmake variables that I can use that would make sense in this situation? Any help would be greatly appreciated. Also, let me know if there and statements or variables set above that I need to remove. Thanks. -- David C. Rankin, J.D.,P.E.

13 years, 10 months

kdebase make failure: iccconfig.cpp:359:37: error: expected ‘,’ or ‘;’

by David C. Rankin

Well, We are making progress. kdebase built through 30% and then died with the following: [ 30%] Generating iccconfig_skel.cpp Scanning dependencies of target kcm_iccconfig-module [ 30%] Building CXX object kcontrol/iccconfig/CMakeFiles/kcm_iccconfig-module.dir/iccconfig.cpp.o /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp: In member function ‘void KICCConfig::load(bool)’: /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp:289:38: error: expected type-specifier /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp:289:38: error: cannot convert ‘int*’ to ‘KRandrSimpleAPI*’ in initialization /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp:289:38: error: expected ‘,’ or ‘;’ /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp: In member function ‘virtual void KICCConfig::save()’: /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp:359:37: error: expected type-specifier /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp:359:37: error: cannot convert ‘int*’ to ‘KRandrSimpleAPI*’ in initialization /home/david/arch/pkg/tbld/kdebase/kcontrol/iccconfig/iccconfig.cpp:359:37: error: expected ‘,’ or ‘;’ make[2]: *** [kcontrol/iccconfig/CMakeFiles/kcm_iccconfig-module.dir/iccconfig.cpp.o] Error 1 make[1]: *** [kcontrol/iccconfig/CMakeFiles/kcm_iccconfig-module.dir/all] Error 2 make: *** [all] Error 2 Aborting... I have no idea what that means. (except it wanted a comma or semi-colon and didn't get it ;-) Progress on this box was ONLY possible because KDE4/Qt4 was NOT installed. On boxes where kde4/Qt4 is installed, the kdebase build fails here: [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/kickerSettings.cpp.o In file included from /usr/include/QtCore/QFile:1:0, from /home/david/arch/pkg/trinity/kdebase/src/kicker/libkicker/kickerSettings.cpp:7: /usr/include/QtCore/qfile.h:53:1: error: ‘QT_BEGIN_HEADER’ does not name a type /usr/include/QtCore/qfile.h:62:27: error: expected initializer before ‘:’ token make[2]: *** [kicker/libkicker/CMakeFiles/kickermain-shared.dir/kickerSettings.cpp.o] Error 1 make[1]: *** [kicker/libkicker/CMakeFiles/kickermain-shared.dir/all] Error 2 make: *** [all] Error 2 Aborting... So how do I tell the build to ignore /usr/include/QtCore? Is this something that needs fixing in the code? I have tried to tell cmake to only use /opt and I have set my path accordingly: build() { msg "Setting PATH, CMAKE and Trinity Environment variables" [[ ${PATH%%:*} =~ /opt/qt/bin ]] || export PATH=/opt/qt/bin:$PATH export CMAKE_PREFIX_PATH=/opt/qt export CMAKE_INCLUDE_PATH=/opt/qt/include:/opt/qt/include/tqt export KDEDIR=/opt/trinity export KDEDIRS=/opt/trinity:/usr export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/trinity/lib/pkgconfig:/opt/qt/lib/pkgconfig export XDG_CONFIG_DIRS=/etc/xdg:/opt/trinity/etc/xdg:/opt/trinity/etc/xdg export XDG_DATA_DIRS=/usr/share/:/usr/local/share/:/opt/trinity/share:/opt/trinity/share msg "Configuring autotools and Creating Makefile.common" cd ${startdir} cp -Rp /usr/share/aclocal/libtool.m4 admin/libtool.m4.in cp -Rp /usr/share/libtool/config/ltmain.sh admin/ltmain.sh make -f admin/Makefile.common # set --enable-closure configure option if needed (needed for kdebase) trinity_prefix="/opt/trinity" ./configure --prefix=${trinity_prefix} \ --includedir=${trinity_prefix}/include/kde \ --mandir=${trinity_prefix}/share/man \ --infodir=${trinity_prefix}/share/info \ --with-extra-libs=${trinity_prefix}/lib \ --sysconfdir=/etc \ --localstatedir=/var \ --libexecdir=${trinity_prefix}/lib/kdebase-kde3 \ --disable-rpath \ --with-xinerama \ --with-qt-dir=/opt/qt \ --with-qt-includes=/opt/qt/include \ --with-qt-libraries=/opt/qt/lib \ --with-extra-includes=/opt/qt/include/tqt \ --enable-closure cd ${srcdir} cmake ../ \ -DCMAKE_INSTALL_PREFIX=${trinity_prefix} \ -DWITH_QT3=ON \ -DBUILD_ALL=ON \ -DCMAKE_SKIP_RPATH=ON make || return 1 } So I'm not sure what to do to keep the build from looking at Qt4. I have several boxes to build on. The current box I'm using (the one that made it to 30%) is an i686 with only kde3, gnome, and fluxbox on it. I was still getting cmake messages like: /opt/trinity/lib/kde3/plugins/designer/kdewidgets.so: Feature KWritePermsIcon already defined in /opt/kde/lib/kde3/plugins/designer/kdewidgets.so! so I have removed kde3 from the box completely and I'm starting over. Any thoughts welcome. Let me know if I need to file something on the iccconfig.cpp issue. Thanks. -- David C. Rankin, J.D.,P.E.

13 years, 10 months

kdebase on x86_64: make: *** No rule to make target `install'. Stop.

by David C. Rankin

I've started a new thread, since this is now a 'make' problem instead of a configure problem. It also looks like this might be an x86_64 issue because I am currently building kdebase on i686 with the *exact* same build scripts and it seems to be working fine. (well until it bombed later -- see at end) Here is the background from the prior thread: >> ==> Packaging - trinity-kdebase-1218548 >> >> make: *** No rule to make target `install'. Stop. >> >> Aborting... >> >> >> >> Looking at the Makefile generated in the out-of-source dir, it does NOT >> >> contain any install: target. Looking at the Makefile in the original >> >> trinity/kdebase directory is does contain install: install-recursive. My >> >> bet is that is what needs to be called. I don't know why kdebase is >> >> exhibiting this behavior with make targets when tqtinterface, arts, and >> >> kdelibs all had no problem with the install: target. Any ideas? I'll try >> >> calling make -f ../Makefile and see if that works. > > > > add "-DBUILD_ALL=ON" to cmake arguments <snip> Hmm... I updated the cmake command to: cmake ../ \ -DCMAKE_INSTALL_PREFIX=${trinity_prefix} \ -DWITH_QT3=ON \ -DBUILD_ALL=ON \ -DCMAKE_SKIP_RPATH=ON make || return 1 I still get the error: config.status: executing libtool commands Good - your configure finished. Start make now -- checking for 'TDE' -- found 'TDE', version 3.5.10 -- Configuring done -- Generating done -- Build files have been written to: /dat_e/david/bld/trinity/kdebase/src ==> Entering fakeroot environment... ==> Determining SVN revision for trinity-kdebase... ==> Starting package()... ==> Packaging - trinity-kdebase-1218548 make: *** No rule to make target `install'. Stop. Aborting... I have put the trinity/kdebase/Makefile here: http://www.3111skyline.com/dl/dt/trinity/errors/kdebase-Makefile the trinity/kdebase/src/Makefile is: http://www.3111skyline.com/dl/dt/trinity/errors/kdebase_src-Makefile the config.log is here: http://www.3111skyline.com/dl/dt/trinity/errors/kdebase-config-3.log I spoke too soon, the i686 build just died as well: [ 11%] Generating kickerSettings.cpp Scanning dependencies of target kickermain-shared [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/appletinfo.cpp.o [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/global.cpp.o [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/kickertip.cpp.o [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/menuinfo.cpp.o [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/panelbutton.cpp.o [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/panner.cpp.o [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/kickerSettings.cpp.o In file included from /usr/include/QtCore/QFile:1:0, from /home/david/arch/pkg/trinity/kdebase/src/kicker/libkicker/kickerSettings.cpp:7: /usr/include/QtCore/qfile.h:53:1: error: ‘QT_BEGIN_HEADER’ does not name a type /usr/include/QtCore/qfile.h:62:27: error: expected initializer before ‘:’ token make[2]: *** [kicker/libkicker/CMakeFiles/kickermain-shared.dir/kickerSettings.cpp.o] Error 1 make[1]: *** [kicker/libkicker/CMakeFiles/kickermain-shared.dir/all] Error 2 make: *** [all] Error 2 Aborting... Judging from the error, it still looks like it is grabbing Qt4 headers (/usr/include/QtCore). I have /opt/qt first in PATH and I have set: export CMAKE_PREFIX_PATH=/opt/qt export CMAKE_INCLUDE_PATH=/opt/qt/include:/opt/qt/include/tqt So I'm not sure how it is grabbing the /usr/include files (it may be OK) Oh well, that's for tomorrow. If you have any thoughts, let me know. Thanks. -- David C. Rankin, J.D.,P.E.

13 years, 10 months

Upgrade stable -> testing -- with errors

by Brad Alexander

I may have just shot myself in the foot, but I decided to go ahead and upgrade my wife's machine. It was running stable (lenny atm) and I wanted to get it to testing. Its running trinity as well. So I updated the apt-conf to APT::Default-Release "testing"; (My base sources.list includes links for all three releases), updated the trinity list from the lenny one to the squeeze one (the ppa format), and I ran aptitude update; aptitude full-upgrade. Things went well for about 30 minutes, then crashed. Now I am getting [root@galaxy archives]# dpkg --configure -a Setting up menu (2.1.41) ... update-menus: symbol lookup error: /usr/lib/libstdc++.so.6: undefined symbol: _ZNSt8messagesIcE2idE, version GLIBCXX_3.4 dpkg: error processing menu (--configure): subprocess post-installation script returned error exit status 127 Setting up python2.6 (2.6.6-8+b1) ... update-menus: symbol lookup error: /usr/lib/libstdc++.so.6: undefined symbol: _ZNSt8messagesIcE2idE, version GLIBCXX_3.4 dpkg: error processing python2.6 (--configure): subprocess post-installation script returned error exit status 127 dpkg: dependency problems prevent configuration of libpython2.6: libpython2.6 depends on python2.6 (= 2.6.6-8+b1); however: Package python2.6 is not configured yet. dpkg: error processing libpython2.6 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: menu python2.6 libpython2.6 and I can't get past the undefined symbol. Can anyone suggest what I need to get this done? Especially since I didn't warn my wife what I was doing? Thanks, --b

13 years, 10 months

kdebase still fails ./configure - configure:24540: /opt/qt/bin/uic-tqt -L... test

by David C. Rankin

Serghei, All, After starting over from the beginning with tqtinterface installed in /opt/qt, kdebase fails to ./configure. The config.log error is: configure:24474: result: libraries /opt/trinity/lib, headers /opt/trinity/include configure:24513: checking if UIC has KDE plugins available configure:24540: /opt/qt/bin/uic-tqt -L /opt/trinity/lib/kde3/plugins/designer -nounload -impl actest.h actest.ui > actest.cpp Qt User Interface Compiler version 4.7.1 Usage: uic [options] <uifile> -h, -help display this help and exit -v, -version display version -d, -dependencies display the dependencies -o <file> place the output into <file> -tr <func> use func() for i18n -p, -no-protection disable header protection -n, -no-implicit-includes disable generation of #include-directives for forms generated by uic3 -g <name> change generator configure:24543: $? = 0 configure:24557: result: no configure:24560: error: you need to install kdelibs first. If you did install kdelibs, then the Qt version that is picked up by this configure is not the same version you used to compile kdelibs. The Qt Plugin installed by kdelibs is *ONLY* loadable if it is the _same Qt version_, compiled with the _same compiler_ and the same Qt configuration settings. full config.log: http://www.3111skyline.com/dl/dt/trinity/errors/kdebase-config-2.log Huh? I'm not sure what I'm missing here. I look at /opt/trinity/lib/kde3/plugins/designer and all I find is: 17:36 archangel:/dat_e/david/bld/trinity/kdebase> l /opt/trinity/lib/kde3/plugins/designer total 116 drwxr-xr-x 2 root root 4096 Feb 2 16:42 . drwxr-xr-x 4 root root 4096 Feb 2 16:42 .. -rw-r--r-- 1 root root 770 Feb 2 16:22 kdewidgets.la -rwxr-xr-x 1 root root 99568 Feb 2 16:42 kdewidgets.so Anybody have an idea why kdebase is throwing this error? Is it grabbing the wrong UI Compiler? Help? -- David C. Rankin, J.D.,P.E.

13 years, 10 months

Konqueror web view location toolbar missing

by John A. Sullivan III

I'm feeling pretty stupid again. Is it my imagination or, when I click on Konqueror under Internet as a web browser or click on the Web Browser desktop icon, the Location toolbar is missing and nowhere to be found. If I open Konqueror as a file browser and switch the view to web browser, the Location bar is there as expected. Thanks - John

13 years, 10 months

tqt in /opt/qt, kdelibs cmake - tqt.h not found??

by David C. Rankin

OK, 2 steps forward 3 steps back. I've rebuilt tqtinterface to install in /opt/qt consistent with Qt3-3.3.8c and all executables are there: 14:52 archangel:/dat_e/david/bld/trinity/kdelibs> ls -1 /opt/qt/bin/ assistant convert_qt_tqt1 convert_qt_tqt2 convert_qt_tqt3 dcopidl-tqt dcopidl2cpp-tqt dcopidlng-tqt designer linguist lrelease lupdate mcopidl-tqt moc moc-tqt qm2ts qmake qt3config qtconfig tmoc tqt-replace tqt-replace-stream uic uic-tqt The tqt.h header is in /opt/qt/include/tqt: 15:20 archangel:/dat_e/david/bld/trinity/kdelibs> l /opt/qt/include/tqt/tqt.h -rw-r--r-- 1 root root 57672 Feb 1 12:06 /opt/qt/include/tqt/tqt.h arts built fine with: trinity_prefix="/opt/trinity" ./configure --prefix=${trinity_prefix} \ --includedir=${trinity_prefix}/include/kde \ --mandir=${trinity_prefix}/share/man \ --infodir=${trinity_prefix}/share/info \ --with-extra-libs=${trinity_prefix}/lib \ --sysconfdir=/etc \ --localstatedir=/var \ --libexecdir=${trinity_prefix}/lib/kdebase-kde3 \ --with-qt-dir=/opt/qt \ --with-qt-includes=/opt/qt/include \ --with-qt-libraries=/opt/qt/lib \ --disable-rpath cd ${srcdir} cmake ../ \ -DCMAKE_INSTALL_PREFIX=${trinity_prefix} \ -DWITH_QT3=ON \ -DCMAKE_SKIP_RPATH=ON make but now kdelibs fails saying it can't find tqt.h? The error is: Good - your configure finished. Start make now -- Found x86 architecture -- Found Cups: /usr/lib/libcups.so -- Configuring done -- Generating done -- Build files have been written to: /dat_e/david/bld/trinity/kdelibs/src [ 1%] Built target kICE-static [ 1%] Building CXX object dcop/CMakeFiles/DCOP-shared.dir/dcopstub.cpp.o cc1plus: fatal error: tqt.h: No such file or directory compilation terminated. make[2]: *** [dcop/CMakeFiles/DCOP-shared.dir/dcopstub.cpp.o] Error 1 make[1]: *** [dcop/CMakeFiles/DCOP-shared.dir/all] Error 2 make: *** [all] Error 2 Aborting... It found it fine when tqtinterface used -DCMAKE_INSTALL_PREFIX=/usr. Googling, I tried 'export CMAKE_PREFIX_PATH=/opt/qt', but that made no difference. I have adjusted the ./configure options a number of times even specifying '--with-extra-includes=/opt/qt/include/tqt' to explicitly point to where tqt.h is installed, but still no joy. I was using the following on the last attempt: trinity_prefix="/opt/trinity" ./configure --prefix=${trinity_prefix} \ --includedir=${trinity_prefix}/include/kde \ --mandir=${trinity_prefix}/share/man \ --infodir=${trinity_prefix}/share/info \ --with-extra-libs=${trinity_prefix}/lib \ --sysconfdir=/etc \ --localstatedir=/var \ --libexecdir=${trinity_prefix}/lib/kdebase-kde3 \ --with-qt-dir=/opt/qt \ --with-qt-includes=/opt/qt/include \ --with-qt-libraries=/opt/qt/lib \ --with-extra-includes=/opt/qt/include/tqt \ --disable-rpath cd ${srcdir} cmake ../ \ -DCMAKE_INSTALL_PREFIX=${trinity_prefix} \ -DWITH_QT3=ON \ -DCMAKE_SKIP_RPATH=ON make Any ideas on how to get kdelibs to find tqt.h? Configure finished fine, but here is the config.log in case it hold clues: http://www.3111skyline.com/dl/dt/trinity/errors/kdelibs-config.log.bz2 Any help will be greatly appreciated. -- David C. Rankin, J.D.,P.E.

13 years, 10 months

kdelibs OK, kdebase ./configure fails - attempting to compile Trinity without the Trinity Qt Interface

by David C. Rankin

Hmm... I'm beginning to suspect that I have tqtinterface installed in the wrong place. I build tqtinterface with: cmake ../ \ -DCMAKE_INSTALL_PREFIX=/usr \ -DWITH_QT3=ON \ -DCMAKE_SKIP_RPATH=ON || return 1 And I have built arts and kdelibs with: cmake ../ \ -DCMAKE_INSTALL_PREFIX=/opt/trinity \ -DWITH_QT3=ON \ -DCMAKE_SKIP_RPATH=ON make kdelibs built OK, but both kdebase and kdebindings (not needed I know) fail during ./configure with: checking for uic-tqt... /usr/bin/uic-tqt checking whether uic supports -L ... yes checking whether uic supports -nounload ... yes checking if TQt is available... no configure: WARNING: You are attempting to compile Trinity without the Trinity Qt Interface installed. Please install libtqtinterface-dev and try again! checking if Qt needs -ljpeg... no checking for rpath... no checking for KDE... libraries /opt/trinity/lib, headers /opt/trinity/include checking if UIC has KDE plugins available... no configure: error: you need to install kdelibs first. I do have kde4 on this box with qt 4.7.1-3 which installs to /usr, so I then tried the following configure options with kdebase: --with-qt-dir=/usr/bin \ --with-qt-includes=/usr/include/tqt \ --with-qt-libraries=/usr/lib \ Which caused the following ./configure error: checking for libjpeg... -ljpeg checking for perl... /usr/bin/perl checking for Qt... configure: error: Qt (>= Qt 3.3 and < 4.0) (library qt-mt) not found. Please check your installation! For more details about this problem, look at the end of config.log. Make sure that you have compiled Qt with thread support! Hmm... again... Looking where qt-mt got installed, I find: 2:52 providence:~/arch/pkg/trinity/dependencies/tqtinterface> find /opt/qt/ -name "*qt-mt*" /opt/qt/lib/libqt-mt.so.3 /opt/qt/lib/pkgconfig/qt-mt.pc /opt/qt/lib/libqt-mt.so /opt/qt/lib/libqt-mt.so.3.3.8 /opt/qt/lib/libqt-mt.so.3.3 /opt/qt/lib/libqt-mt.prl which are the new qt3-3.3.8c libraries. I then rebuilt tqtinterface to go in /opt/qt. But then remaking arts failed not finding Qt again. Grrr.... I then rebuilt tqtinterface with PREFIX=/usr. But now when I'm back to square one and kdebase, ./configure fails... So, what's the solution? Should I remake tqtinterface with -DCMAKE_INSTALL_PREFIX=/opt/qt and then try adjusting the --with-qt... options for all remaining packages? Is there an environment variable trick I can try? What say the experts? -- David C. Rankin, J.D.,P.E.

13 years, 10 months

kdebase option --with-pam (use it?)

by David C. Rankin

All, What is the current thinking of compiling kdebase '--with-pam'? The README lists the option: `--with-pam[=ARG]' enable support for PAM: ARG=[yes|no|service name] According to the README, the --with designation implies that it is OFF by default. Is this functionality desired in trinity? I ask, because I don't know whether it is enabled on my current kde3 install, but if it is useful, I want it :) What say the gurus? -- David C. Rankin, J.D.,P.E.

13 years, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users