tde-users

users@trinitydesktop.org

4290 discussions

Clean Build Env. In Vbox - arts fails: libmcop.so.1 No such file or directory
by David C. Rankin 06 Feb '11

06 Feb '11

Hello list, To get around some of the strange kdebase build failures on Arch Linux, I create a fresh virtual machine in VirtualBox with a minimal install (X and fluxbox) to build Trinity in a clean build environment. Qt3 and tqtinterface build fine. We have run into an arts build failure where it won't use the shared library in its own directory. The error I get is: /usr/bin/ranlib libgsl.a make[2]: Leaving directory `/home/david/tbld/dependencies/arts/src' /usr/bin/cmake -E cmake_progress_report /home/david/tbld/dependencies/arts/src/CMakeFiles 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 [ 48%] Built target gsl-static make -f flow/CMakeFiles/artsflow_idl-shared.dir/build.make flow/CMakeFiles/artsflow_idl-shared.dir/depend make[2]: Entering directory `/home/david/tbld/dependencies/arts/src' /usr/bin/cmake -E cmake_progress_report /home/david/tbld/dependencies/arts/src/CMakeFiles [ 48%] Generating artsflow.cc cd /home/david/tbld/dependencies/arts/src/flow && ../mcopidl/mcopidl -t /home/david/tbld/dependencies/arts/flow/artsflow.idl ../mcopidl/mcopidl: error while loading shared libraries: libmcop.so.1: cannot open shared object file: No such file or directory make[2]: *** [flow/artsflow.cc] Error 127 make[2]: Leaving directory `/home/david/tbld/dependencies/arts/src' make[1]: *** [flow/CMakeFiles/artsflow_idl-shared.dir/all] Error 2 make[1]: Leaving directory `/home/david/tbld/dependencies/arts/src' make: *** [all] Error 2 Aborting... libmcop.so.1 is readily available in the mcop directory, so I don't understand the error: 17:47 trinity:~/tbld/dependencies/arts> find . -name libmcop.so.1 ./src/mcop/libmcop.so.1 My cmake environment and arguments are: export CMAKE_PREFIX_PATH=/opt/qt export CMAKE_INCLUDE_PATH=/opt/qt/include:/opt/qt/include/tqt trinity_prefix="/opt/trinity" cd ${srcdir} cmake ../ \ -DCMAKE_INSTALL_PREFIX=${trinity_prefix} \ -DQT_LIBRARY_DIRS=/opt/qt/lib \ -DCMAKE_SKIP_RPATH=ON make VERBOSE=1 The two exports and -DQT_LIBRARY_DIRS=/opt/qt/lib are required or cmake will not find the patched Qt3 (that may be normal, I don't know) Any ideas on how to get arts to see its libmcop.so.1? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

2 2

kaffeine version numbers
by Dexter Filmore 06 Feb '11

06 Feb '11

The new kaffeine packages do not have increased version numbers. Now the system always tries to overwrite my custom packages. Advice? Dex -- -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS d--(+)@ s-:+ a C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K- w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ b++(+++) DI+++ D- G++ e* h>++ r* y? ------END GEEK CODE BLOCK------

1 0

building Trinity in a chroot [was: kdebase make failure if Qt4 installed...]
by David C. Rankin 05 Feb '11

05 Feb '11

On 02/04/2011 02:34 PM, Serghei Amelian wrote: > Ensure that kickerSettings.cpp is not generated by Qt4 uic. To avoid these > stange problems, I suggest to use a virtual machine or chroot with clean > setup. > Which do you recommend? I have VirtualBox installed and could create another Arch Linux guest, or I could try and setup a chroot environment. I know how to do the virtual machine, but I'm interested in the chroot. (saves updating the guest install) I know how to chroot my OS, but I've never created a chroot to build packages. Would I just need to setup a fakeroot environment somewhere with: fakeroot /opt/qt /opt/trinity /home/trinity-svn (and what else??) I'll google it, but if you have a favorite link, I'll take it :) -- David C. Rankin, J.D.,P.E.

2 2

kdebase iccconfig.cpp make failure - Round 2
by David C. Rankin 04 Feb '11

04 Feb '11

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.

2 5

kdebase make failure if Qt4 installed, QtCore/qfile.h QT_BEGIN_HEADER doesn't name type
by David C. Rankin 04 Feb '11

04 Feb '11

[ 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.

2 5

kdebase make failure: iccconfig.cpp:359:37: error: expected ‘,’ or ‘;’
by David C. Rankin 03 Feb '11

03 Feb '11

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.

2 4

kdebase on x86_64: make: *** No rule to make target `install'. Stop.
by David C. Rankin 03 Feb '11

03 Feb '11

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.

2 2

Upgrade stable -> testing -- with errors
by Brad Alexander 03 Feb '11

03 Feb '11

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

4 3

kdebase still fails ./configure - configure:24540: /opt/qt/bin/uic-tqt -L... test
by David C. Rankin 03 Feb '11

03 Feb '11

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.

2 4

Konqueror web view location toolbar missing
by John A. Sullivan III 03 Feb '11

03 Feb '11

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

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users