tde-devels

devels@trinitydesktop.org

6 participants
3840 discussions

Building PyKDE3 (Solved???)
by Darrell Anderson 28 Mar '11

28 Mar '11

I made some progress with building PyKDE3. I had to cheat. I think. The problem seems to be that building Trinity to install in /opt/trinity confuses the PyKDE3 build process. Last autumn when I built Trinity 3.5.12 to install in /usr I had no problems building PyKDE3. Since then I have not tried to build any packages to install in /usr. I have been focusing on installing in /opt/trinity in order to coexist with KDE4/QT4. When Trinity is installed in /opt/trinity the build always fails with this kind of error: ========================================= /usr/bin/ld: cannot find -lDCOP collect2: ld returned 1 exit status make[1]: *** [dcop.so] Error 1 make[1]: Leaving directory `/dev/shm/PyKDE-3.16.7/dcop' make: *** [all] Error 2 ========================================= I then create a sym link in /usr/lib to the allegedly not found library: ln -s /opt/trinity/lib/libDCOP.so libDCOP.so The next build proceeds past that error but again fails with a similar not found error message about the next module, kdecore. I create another sym link. The package proceeds to build to the next module, kdefx, and again fails. Rinse. Repeat. For each module: dcop kdecore kdefx kdeui kio kresources kabc kutils kfile kparts khtml kspell kdeprint kmdi I modified my build script to temporarily create the sym links on-the-fly and remove them after make completes. The package then builds without failure. Yet I wonder whether this will break the package libraries. Are they linked to /usr/lib rather than /opt/trinity/lib? Seems something in the PyKDE3 configuration is hard-coded to /usr/lib. I already have the following in my build script: sed -i -e "s:/usr:${PREFIX}:" configure.py where $PREFIX is /opt/trinity /etc/ld.so.conf contains /opt/trinity/lib, which was inserted from the kdelib package (and runs ldconfig, but I have run ldconfig manually too). Running ldconfig -v shows the allegedly not found libraries in /opt/trinity/lib. The build script configure output says the following: KDE base directory is /opt/trinity KDE include directory is /opt/trinity/include KDE lib directory is /opt/trinity/lib/kde3 lib directory is /opt/trinity/lib Everything seems to indicate the libraries should be found. Yet the package refuses to build without the temporary sym links. Seems make should find the libraries in /opt/trinity/lib. Exporting LD_LIBRARY_PATH in the build script does not help. Any ideas what is happening? Any ideas how to fix? Darrell

3 4

Amarok Build Options
by Darrell Anderson 28 Mar '11

28 Mar '11

I notice in the Amarok CMakeLists.txt there are several missing build options that were available in automake: --with-libnjb --with-libmtp --with-libkarma --with-mp4v2 --without-musicbrainz --without-daap --disable-amazon For myself I have no need for syncing to devices or sharing music. Would be nice to build Amarok without that overhead. :) I realize a lot of work is going on with everything. I thought I'd mention this and hopefully the options are added eventually. Thanks. Darrell

2 1

Tin Need help with 3.5.12 automake files
by Darrell Anderson 27 Mar '11

27 Mar '11

Tim, I am able to build all of the same 3.5.12 packages I built last autumn except PyKDE3, Digikam, and Gwenview. I already submitted a post about PyKDE3 (help is appreciated!). The primary difference this time that the builds are failing is I am trying to install the Trinity/KDE packages into /opt/trinity rather than /usr. Some library and support packages, such as sip, PyQT3, PyKDE3, libical, libcaldav, etc., I am still installing in /usr and /usr/lib. Digikam FTBFS with this error: ==================== grep: /usr/lib/libkdecore.la: No such file or directory /usr/bin/sed: can't read /usr/lib/libkdecore.la: No such file or directory libtool: link: `/usr/lib/libkdecore.la' is not a valid libtool archive ==================== Gwenview FTBFS with this error: ==================== grep: /usr/lib/libkio.la: No such file or directory /usr/bin/sed: can't read /usr/lib/libkio.la: No such file or directory libtool: link: `/usr/lib/libkio.la' is not a valid libtool archive ==================== Notice the builds are trying to find those files in /usr/lib rather than /opt/trinity/lib. Something in the configuration files is hard-coded to /usr/lib. I realize 3.5.12 is more or less etched in stone, but the cmake conversion will take time. All I need is a patch that I can merge on-the-fly in my build scripts to ensure automake looks in the correct location. Besides, neither of these packages have been converted to cmake yet and probably won't be for some time. Maybe the problem is an environment variable, although all of the other packages compiled fine. I want to get all of these 3.5.12 packages to build in Slackware 12.2 with /opt/trinity. Once proven they will build, install, and run there I then will start the testing the build process with the next Slackware release, which are required to get installed in a location other than /usr. This is very much proof of concept before moving to the next step. Not to mention that in the next step I need to build qt3 too. Should anyone start quashing bugs with the core or main suite packages I can rebuild Trinity packages in 12.2 and test those patches immediately. I also should be able to install Trinity 3.5.12 alongside KDE 3.5.10 in 12.2, which will help all of us with troubleshooting and comparisons to KDE3. Thanks much! Darrell

1 1

trinity-kdebase [ 81%] Built
by Castro 27 Mar '11

27 Mar '11

Hi Serghei, I am learning something about Cmake. :-) I've added few files to your cmake modules. FindXcomposite.cmake FindXFixes.cmake FindXrender.cmake FindXdamage.cmake FindXinerama.cmake This one should be simple but I have run out of steam. :-( Started work at 2am, it is 5pm! Time for a pint or two. :-) [ 81%] Built target ksplashredmond-module Linking CXX executable ksplashsimple /usr/bin/ld: cannot find -ltqt /usr/bin/ld: cannot find -lqt-mt collect2: ld returned 1 exit status make[2]: *** [ksplashml/themeengine/simple/ksplashsimple] Error 1 make[1]: *** [ksplashml/themeengine/simple/CMakeFiles/ksplashsimple.dir/all] Error 2 make: *** [all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... [castro@castro2 trinity-kdebase]$ Castro.

2 3

KDEBASE - Build error
by Baho Utot 27 Mar '11

27 Mar '11

I am having the following problem: [ 55%] Building CXX object ksplashml/themeengine/simple/CMakeFiles/ksplashsimple.dir/main.cpp.o Linking CXX executable ksplashsimple /usr/bin/ld: cannot find -ltqt /usr/bin/ld: cannot find -lqt-mt collect2: ld returned 1 exit status make[2]: *** [ksplashml/themeengine/simple/ksplashsimple] Error 1 make[1]: *** [ksplashml/themeengine/simple/CMakeFiles/ksplashsimple.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... [ 55%] Building CXX object ksmserver/CMakeFiles/kdeinit_ksmserver-shared.dir/shutdown.cpp.o [ 55%] Building CXX object ksmserver/CMakeFiles/kdeinit_ksmserver-shared.dir/client.cpp.o [ 56%] Building CXX object ksmserver/CMakeFiles/kdeinit_ksmserver-shared.dir/KSMServerInterface_skel.cpp.o [ 56%] Building CXX object ksmserver/CMakeFiles/kdeinit_ksmserver-shared.dir/server_skel.cpp.o [ 56%] Building CXX object ksmserver/CMakeFiles/kdeinit_ksmserver-shared.dir/timed.cpp.o Linking CXX shared library libkdeinit_ksmserver.so [ 56%] Built target kdeinit_ksmserver-shared make: *** [all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... Build failed, check /home/build/scrat/build make: *** [KDEBASE] Error 1 I don't understand why this is failing here as other modules are not failing. The patched qt3 is install and so is tqtinterface, the packages that contain the libarayies in question. I have looked at the CmakeLists.txt for serveral modules and compared them to the one in ksplashsimple and I don't see anything that would cause this error. Since I don't know cmake I am stuck at this time. Where is this set ie ${TQT_LIBRARY_DIRS} link_directories( ${TQT_LIBRARY_DIRS} ) If anyone could point me in the right direction and maybe explain about how cmake finds libaries I would be grateful. I want to learn this in case of future problems. I am going to purchase a book on cmake in the future when I get the money to do so. Thanks

1 0

trinity-tqtinterface and trinity-kdebase
by Castro 27 Mar '11

27 Mar '11

Tim, Can I suggest the following change to tqt.h #ifndef USE_QT3 #define USE_QT3 #endif Castro. My setup. Archlinux with TDE-3.5.13 running on VirtualBox. Out of source builds. ############################################### Serghei, I think this one's for you. svn 1226116 [ 37%] Building CXX object kwin/data/CMakeFiles/kwin_update_window_settings.dir/update_window_settings.cpp.o Linking CXX executable kwin_update_window_settings [ 37%] Built target kwin_update_window_settings Scanning dependencies of target kompmgr [ 37%] Building C object kwin/kompmgr/CMakeFiles/kompmgr.dir/kompmgr.c.o Linking C executable kompmgr CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `add_damage': kompmgr.c:(.text+0xee): undefined reference to `XFixesUnionRegion' kompmgr.c:(.text+0x100): undefined reference to `XFixesDestroyRegion' CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `determine_mode': kompmgr.c:(.text+0x2c4): undefined reference to `XFixesCreateRegion' kompmgr.c:(.text+0x2dc): undefined reference to `XFixesCopyRegion' CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `win_extents': kompmgr.c:(.text+0x7c6): undefined reference to `XFixesCreateRegion' CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `set_fade.clone.14': kompmgr.c:(.text+0x13a9): undefined reference to `XFixesDestroyRegion' CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `run_fades': kompmgr.c:(.text+0x16db): undefined reference to `XFixesDestroyRegion' CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `finish_unmap_win': kompmgr.c:(.text+0x19a2): undefined reference to `XFixesDestroyRegion' kompmgr.c:(.text+0x1a00): undefined reference to `XFixesDestroyRegion' kompmgr.c:(.text+0x1a38): undefined reference to `XFixesDestroyRegion' CMakeFiles/kompmgr.dir/kompmgr.c.o:kompmgr.c:(.text+0x1a70): more undefined references to `XFixesDestroyRegion' follow CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `add_win': kompmgr.c:(.text+0x1bd1): undefined reference to `XDamageCreate' kompmgr.c:(.text+0x1c7b): undefined reference to `XShapeSelectInput' CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `finish_destroy_win': kompmgr.c:(.text+0x1e1a): undefined reference to `XDamageDestroy' CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `repair_win': kompmgr.c:(.text+0x1fc2): undefined reference to `XFixesCreateRegion' kompmgr.c:(.text+0x1ff1): undefined reference to `XDamageSubtract' kompmgr.c:(.text+0x2010): undefined reference to `XFixesTranslateRegion' kompmgr.c:(.text+0x2076): undefined reference to `XDamageSubtract' kompmgr.c:(.text+0x2094): undefined reference to `XFixesCreateRegion' kompmgr.c:(.text+0x20a7): undefined reference to `XFixesCopyRegion' kompmgr.c:(.text+0x20ca): undefined reference to `XFixesTranslateRegion' kompmgr.c:(.text+0x20e1): undefined reference to `XFixesUnionRegion' kompmgr.c:(.text+0x20f0): undefined reference to `XFixesDestroyRegion' CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `border_size': kompmgr.c:(.text+0x2138): undefined reference to `XFixesCreateRegionFromWindow' kompmgr.c:(.text+0x216b): undefined reference to `XFixesTranslateRegion' CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `paint_all': kompmgr.c:(.text+0x21d1): undefined reference to `XFixesSetPictureClipRegion' kompmgr.c:(.text+0x2361): undefined reference to `XFixesSetPictureClipRegion' kompmgr.c:(.text+0x241b): undefined reference to `XFixesDestroyRegion' kompmgr.c:(.text+0x2504): undefined reference to `XFixesIntersectRegion' kompmgr.c:(.text+0x252f): undefined reference to `XFixesSetPictureClipRegion' kompmgr.c:(.text+0x25cd): undefined reference to `XFixesSetPictureClipRegion' kompmgr.c:(.text+0x265e): undefined reference to `XFixesDestroyRegion' kompmgr.c:(.text+0x2693): undefined reference to `XFixesSetPictureClipRegion' kompmgr.c:(.text+0x272c): undefined reference to `XFixesIntersectRegion' kompmgr.c:(.text+0x2757): undefined reference to `XFixesSetPictureClipRegion' kompmgr.c:(.text+0x2827): undefined reference to `XFixesSetPictureClipRegion' kompmgr.c:(.text+0x2b28): undefined reference to `XFixesSetPictureClipRegion' kompmgr.c:(.text+0x2b6d): undefined reference to `XFixesSubtractRegion' kompmgr.c:(.text+0x2c36): undefined reference to `XFixesCreateRegion' kompmgr.c:(.text+0x2c52): undefined reference to `XFixesCopyRegion' kompmgr.c:(.text+0x2e51): undefined reference to `XFixesCreateRegion' kompmgr.c:(.text+0x2f12): undefined reference to `XFixesDestroyRegion' kompmgr.c:(.text+0x2f41): undefined reference to `XFixesSubtractRegion' kompmgr.c:(.text+0x30b5): undefined reference to `XFixesDestroyRegion' kompmgr.c:(.text+0x30d0): undefined reference to `XFixesDestroyRegion' kompmgr.c:(.text+0x3103): undefined reference to `XFixesDestroyRegion' kompmgr.c:(.text+0x3136): undefined reference to `XFixesDestroyRegion' kompmgr.c:(.text+0x32ce): undefined reference to `XFixesCreateRegion' kompmgr.c:(.text+0x3306): undefined reference to `XFixesIntersectRegion' kompmgr.c:(.text+0x331d): undefined reference to `XCompositeNameWindowPixmap' CMakeFiles/kompmgr.dir/kompmgr.c.o: In function `main': kompmgr.c:(.text+0x414c): undefined reference to `XCompositeQueryVersion' kompmgr.c:(.text+0x4181): undefined reference to `XDamageQueryExtension' kompmgr.c:(.text+0x4265): undefined reference to `XFixesQueryExtension' kompmgr.c:(.text+0x469d): undefined reference to `XCompositeRedirectSubwindows' kompmgr.c:(.text+0x4b42): undefined reference to `XFixesCreateRegion' kompmgr.c:(.text+0x4bc2): undefined reference to `XFixesCreateRegion' kompmgr.c:(.text+0x4be5): undefined reference to `XFixesCopyRegion' kompmgr.c:(.text+0x4f15): undefined reference to `XFixesUnionRegion' kompmgr.c:(.text+0x4f28): undefined reference to `XFixesDestroyRegion' kompmgr.c:(.text+0x53d1): undefined reference to `XFixesDestroyRegion' kompmgr.c:(.text+0x550e): undefined reference to `XFixesDestroyRegion' kompmgr.c:(.text+0x5ab6): undefined reference to `XCompositeRedirectSubwindows' kompmgr.c:(.text+0x5afb): undefined reference to `XShapeQueryExtension' collect2: ld returned 1 exit status make[2]: *** [kwin/kompmgr/kompmgr] Error 1 make[1]: *** [kwin/kompmgr/CMakeFiles/kompmgr.dir/all] Error 2 make: *** [all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... [castro@castro2 trinity-kdebase]$ Thanks to everyone for all your hard work on this project. :-) Castro.

2 2

Estimate When SVN Will Ready
by Darrell Anderson 26 Mar '11

26 Mar '11

How about an estimate when SVN will again be ready to build? I see a lot of work going on with interfacing with QT4, which seems to have rendered SVN unbuildable. I tried building SVN last night and things broke quickly in kdelibs. The error had something to do with tqtinterface. I realize much is happening under the surface but us mushrooms would appreciate a drop of rain now and then. :) Darrell

3 4

dbus-tqt - missing cmake modules
by Baho Utot 26 Mar '11

26 Mar '11

The svn trre for dbus-tqt is missing the following files cmake/modules cmake/modules/FindQt.cmake cmake/modules/FindTDE.cmake cmake/modules/FindTQt.cmake cmake/modules/TDEMacros.cmake cmake/modules/TDESetupPaths.cmake cmake/modules/tde_uic.cmake cmake/modules/template_dummy_cpp.cmake cmake/modules/template_export_library.cmake cmake/modules/template_kdeinit_executable.cmake cmake/modules/template_kdeinit_module.cmake cmake/modules/template_libtool_file.cmake I copied them from kpower to get dbus-tqt to build Thanks

1 0

Re-Write of Qt3 PKGBUILD required for Arch - original script patched 3.3.8 instead of 3.3.8b
by David C. Rankin 26 Mar '11

26 Mar '11

Calvin, Baho, I will re-write the Qt3 PKGBUILD for Arch. The addition of the new 3.3.8c patch disclosed we were building and patching: 3.3.8 -> 3.3.8c instead of patching 3.3.8b -> 3.3.8c The original Arch PKGBUILD for Qt3 has a mess of combined patches contained within 2 .tar.bz2 files: qt-copy-kde-patches.tar.bz2 qt-patches.tar.bz2 Patching 3.3.8b fails with: Hunk #1 succeeded at 155 (offset 3 lines). patching file src/kernel/qprocess.cpp Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file src/kernel/qprocess.cpp.rej That part of the patch is somewhere in the tarballs above. I'll sort through it and put up a clean trinity-qt3 PKGBUILD when I find the issue. If you try and apply the new part of the trinity qt3_3.3.8c.diff you will find it fails on: -#define QT_VERSION_STR "3.3.8b" because the source the Arch PKGBUILD pulls is: -#define QT_VERSION_STR "3.3.8" Just FYI... -- David C. Rankin, J.D.,P.E.

2 7

openexr are requested, but not found on your system
by Darrell Anderson 25 Mar '11

25 Mar '11

I received the following message while trying to build arts from svn 1225868: "openexr are requested, but not found on your system" Serghei, I know English is not your primary language :). I suggest the following text: "The openexr package was requested but not found on your system." I have nothing against the warning but the build should not have stopped. There does not seem to be option in the arts CMakeLists.txt file to build without OpenEXR nor does the build simply pass through when not finding that package. The OpenEXR package is commonly installed but has never been required in KDE 3.5.10 or Trinity. If that package is now a Trinity prerequisite, then let's pass the word here and I'll be happy to update the wiki. :) Darrell

1 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels