tde-devels

devels@trinitydesktop.org

3753 discussions

Amarok - dependency tunepimp (libtunepimp) deprecated/FTBFS gcc 4.7.1

by David C. Rankin

All, The latest amarok failure I experienced was due to tunepimp (an amarok dep) failing to be available any longer from Arch. Looking further at the musicbrainz.org site, tunepimp is deprecated and new development should not occur with the library due to the RDF database lookup no longer being supported. Further information is here: http://musicbrainz.org/doc/History:libtunepimp/Download Attempting to build tunepimp results in failure on gcc 4.7.1: g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include/tunepimp-0.5 -I../../libltdl -Wall -O2 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -MT mp4.lo -MD -MP -MF .deps/mp4.Tpo -c mp4.cpp -fPIC -DPIC -o .libs/mp4.o mp4.cpp:53:1: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings] <snip> mp4.cpp: In function 'int mp4ReadMetadata(metadata_t*, const char*, int, const char*)': mp4.cpp:124:41: error: 'MP4GetMetadataName' was not declared in this scope <snip many others> Apparently tunepimp has been replaced with one of the following: http://musicbrainz.org/doc/Picard_Tagger http://musicbrainz.org/doc/Classic_Tagger http://musicbrainz.org/doc/CD_Lookup_Tool I know nada about figuring out which one of the new musicbraiz lookups would be the one that amarok will need. What say the experts on how to fix amarok? -- David C. Rankin, J.D.,P.E.

12 years, 7 months

FTBFS tqca-tls (x86_64) can't find TQt3 (i686 builds?)

by David C. Rankin

Tim, All, I just started a full x86_64 build. 1st since name change and I've hit a snag with tqca-tls. My /etc/profile.d/tqt.sh is executable this time :) The build can't find TQt: ==> Setting PATH and Trinity Environment variables ==> Patching... ==> Starting configure... Configuring qca-tls ... Verifying TQt 3.x Multithreaded (MT) build environment ... fail There was an error compiling 'conf'. Be sure you have a proper TQt 3.x Multithreaded (MT) build environment set up. ==> ERROR: A failure occurred in build(). Aborting... HuH?? Looking at the conf.log it looks like a bad joke on 64 bit boxes concerning what was generated: g++ -c -pipe -Wall -W -O2 -D_REENTRANT -DX11_INC='"/usr/X11R6/include"' -DX11_LIBDIR='"/usr/X11R6/lib64"' -DX11_LIB='"-lXext -lX11 -lm"' -DCC='"gcc"' -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -I/opt/tqt3/mkspecs/default -I. -I'/usr/include/tqt' -I/opt/tqt3/include -I/usr/X11R6/include -o conf.o conf.cpp g++ -Wl,-rpath,/opt/tqt3/lib64 -o conf conf.o -L/opt/tqt3/lib64 -L/usr/X11R6/lib64 -ltqt-mt -lXext -lX11 -lm -lpthread /usr/bin/ld: cannot find -ltqt-mt collect2: error: ld returned 1 exit status make: *** [conf] Error 1 Where is this /opt/tqt3/lib'64' garbage coming from? Arch just 'lib' not any 'lib64' dir names when handling libraries. Where in this package are the 'lib' or 'lib64' search directories and lib directory names controlled? Like noted earlier, I can build tqca-tls on i686 all day long, but this is one of the first i've built on x86_64 and something isn't quite right. Prior to the name change stuff, this built like clockwork. Where should we look for the culprit here (there isn't much here). What say the gurus? Ideas? -- David C. Rankin, J.D.,P.E.

12 years, 7 months

tdesdk FTBFS: svn_client-1 library was not found on your system

by Darrell Anderson

The build failure message: -- Looking for svn_pool_create_ex in svn_client-1 -- Looking for svn_pool_create_ex in svn_client-1 - not found CMake Error at cmake/modules/TDEMacros.cmake:23 (message): ################################################# svn_client-1 library was not found on your system. Subversion is installed? Try to set SVN_LIBRARY_DIR to subversion library directory. ################################################# Call Stack (most recent call first): kioslave/svn/ConfigureChecks.cmake:27 (tde_message_fatal) kioslave/svn/CMakeLists.txt:12 (include) The configure test is from tdesdk/kioslave/svn/ConfigureChecks.cmake. David ran into this failure in March. Until recently I was using automake to build tdesdk. After some cmake build bugs were resolved I moved to cmake. tdesdk builds without this specific failure using cmake on Slackware 13.1 and 13.37, both 32 and 64-bit. Those releases use subversion 1.6.16. Slackware Current bumped the subversion package to version 1.7.5. I suspect this is the cause of the failure. Looking at the packages between the two, the libsvn_client-1 lib files are installed in the same location, /usr/lib/. All header files are installed in the same location, /usr/include/subversion-1/. Because Slackware Current is the testing branch for the next release, there is a possibility the package is not built correctly, but because David experienced this failure in March, I am discounting that possibility. Of course, there could be an upstream problem with the way the package builds that would be common downstream to all packagers. tdesdk builds without incident using automake and as far as I can tell, all svn support was built. At this point looks like we need to modify tdesdk/kioslave/svn/ConfigureChecks.cmake. Any ideas? Darrell

12 years, 7 months

x86_64 Arch build report - slow start, but majority OK

by David C. Rankin

Darrell, Tim, After a slow start today in my x86_64 build run on Arch, most packages built. The build failures I experienced after patching the makespec++-64/qmake.conf lib64/lib issue were: 14 Failures: mlt mlt++ (both mlt & mlt++ are OK on i686) tdebindings amarok kchmviewer kdmtheme kbfx kima kstreamripper krusader kmplayer (I think this will build -- will have to tweak) kuickshow digikam (libpng15 issue) koffice On the succeeded side of the equation = 72: hal-0.5.14-9-x86_64.pkg.tar.xz hal-info-0.20091130-6-any.pkg.tar.xz libkarma-0.1.2-1-x86_64.pkg.tar.xz libnjb-2.2.7-2-x86_64.pkg.tar.xz libutempter-1.1.5-8-x86_64.pkg.tar.xz mt-daapd-0.2.4.2-7-x86_64.pkg.tar.xz tde-abakus-14.0.0_dev-1-x86_64.pkg.tar.xz tde-arts-14.0.0_dev-1-x86_64.pkg.tar.xz tde-avahi-tqt-14.0.0_dev-1-x86_64.pkg.tar.xz tde-basket-1.0.3-1-x86_64.pkg.tar.xz tde-dbus-1-tqt-14.0.0_dev-1-x86_64.pkg.tar.xz tde-dbus-tqt-14.0.0_dev-1-x86_64.pkg.tar.xz tde-dolphin-14.0.0_dev-1-x86_64.pkg.tar.xz tde-filelight-14.0.0_dev-1-x86_64.pkg.tar.xz tde-gtk-qt-engine-14.0.0_dev-1-x86_64.pkg.tar.xz tde-gwenview-14.0.0_dev-1-x86_64.pkg.tar.xz tde-k3b-14.0.0_dev-1-x86_64.pkg.tar.xz tde-k9copy-14.0.0_dev-1-x86_64.pkg.tar.xz tde-kaffeine-14.0.0_dev-1-x86_64.pkg.tar.xz tde-kbarcode-14.0.0_dev-1-x86_64.pkg.tar.xz tde-kbookreader-14.0.0_dev-1-x86_64.pkg.tar.xz tde-kdiff3-14.0.0_dev-1-x86_64.pkg.tar.xz tde-kdirstat-14.0.0_dev-1-x86_64.pkg.tar.xz tde-kgtk-qt3-14.0.0_dev-1-x86_64.pkg.tar.xz tde-kio-locate-14.0.0_dev-1-x86_64.pkg.tar.xz tde-kipi-plugins-14.0.0_dev-1-x86_64.pkg.tar.xz tde-knemo-14.0.0_dev-1-x86_64.pkg.tar.xz tde-knetload-14.0.0_dev-1-x86_64.pkg.tar.xz tde-knetstats-14.0.0_dev-1-x86_64.pkg.tar.xz tde-knutclient-14.0.0_dev-1-x86_64.pkg.tar.xz tde-konversation-14.0.0_dev-1-x86_64.pkg.tar.xz tde-kpowersave-14.0.0_dev-1-x86_64.pkg.tar.xz tde-krename-14.0.0_dev-1-x86_64.pkg.tar.xz tde-ksplash-engine-moodin-14.0.0_dev-1-x86_64.pkg.tar.xz tde-libart-lgpl-14.0.0_dev-1-x86_64.pkg.tar.xz tde-libcaldav-14.0.0_dev-1-x86_64.pkg.tar.xz tde-libcarddav-14.0.0_dev-1-x86_64.pkg.tar.xz tde-libkdcraw-14.0.0_dev-1-x86_64.pkg.tar.xz tde-libkexiv2-14.0.0_dev-1-x86_64.pkg.tar.xz tde-libkipi-14.0.0_dev-1-x86_64.pkg.tar.xz tde-libksquirrel-14.0.0_dev-1-x86_64.pkg.tar.xz tde-python-tqt-14.0.0_dev-1-x86_64.pkg.tar.xz tde-rosegarden-14.0.0_dev-1-x86_64.pkg.tar.xz tde-sip-14.0.0_dev-1-x86_64.pkg.tar.xz tde-sip4-tqt-14.0.0_dev-1-x86_64.pkg.tar.xz tde-soundkonverter-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tde-style-qtcurve-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdeaccessibility-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdeaddons-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdeadmin-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdeartwork-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdebase-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdeedu-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdegames-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdegraphics-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdelibs-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdemultimedia-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdenetwork-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdepim-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdesdk-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdesvn-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdetoys-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdeutils-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdevelop-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tdewebdev-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tqca-tls-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tqt3-14.0.0_dev-1-x86_64.pkg.tar.xz tde-tqtinterface-14.0.0_dev-1-x86_64.pkg.tar.xz tde-twin-style-crystal-14.0.0_dev-1-x86_64.pkg.tar.xz tde-wlassistant-14.0.0_dev-1-x86_64.pkg.tar.xz tde-yakuake-14.0.0_dev-1-x86_64.pkg.tar.xz xmedcon-0.11.0-1-x86_64.pkg.tar.xz We will adjust the build of TQt3 to solve the mkspec issue and we should be in good shape. Have a good evening. -- David C. Rankin, J.D.,P.E.

12 years, 7 months

Update script

by Julius Schwartzenberg

Hi Darrell, I just updated my system here and while I have a starttde that refers to a TDEDIR/bin/r14-xdg-update, this file does not exist here (/opt/trinity/bin/r14-xdg-update). Is it in another package somehow? Another note, about the name. On at least Ubuntu and Debian most update scripts are named "update-something". I don't know if this is a convention, but it would be what I expect. Doesn't really matter much though. (Something like update-kde3-to-tder14-profile seems kinda long, but it makes sense about what it does.) Best regards, Julius

12 years, 7 months

Francois: 3.5.13.1 packages

by Darrell Anderson

Francois, Where do you keep your 3.5.13.1 packages online? Would you please provide that information in bug report 1062? http://bugs.pearsoncomputing.net/process_bug.cgi Merci! Darrell

12 years, 7 months

Trinity FAQs

by Darrell Anderson

This past winter we discussed adding an FAQ to the web site. We drafted a starter document that is posted in the etherpad repository. The Trinity help handbook includes an FAQ (bottom of table of contents). That FAQ needs revision attention, which I am addressing. Currently the nature of the two FAQs are different. The proposed FAQ in the etherpad repository was written in large response to quashing conflicts between advocates of Trinity and advocates of KDE4. That FAQ is largely focused on that response. The help handbook FAQ is generic. One FAQ reduces overhead and maintenance. Do we want that? If yes then please provide some cursory reviews of both documents and provide appropriate comments to merge the two documents. Thank you. Darrell

12 years, 7 months

Which platforms does Trinity support?

by Darrell Anderson

The Welcome help handbook says the following: TDE is a graphical desktop environment for UNIX® workstations. The Trinity Desktop Environment combines ease of use, contemporary functionality, and professional graphical design along with the technical advantages of the UNIX® operating system. The underlying KDE3 source code supported many Unix-like Operating systems. Are we still supporting anything other than Linux based systems? I want to make the handbook statement technically correct. "Unix and Unix-like" systems? "Unix, Unix-like, and Linux based" systems? Darrell

12 years, 7 months

pytdeextensions: undefined symbol?

by Darrell Anderson

I am build TDE in Slackware 13.37 32-bit. Thus far all packages are build except pytdeextensions, which build without error in Slackware 13.1 32-bit and 64-bit. The build failure: compiling Qt-Designer UI /var/tmp/package-pytdeextensions/opt/trinity/share/apps/pytdeextensions/app_templates/kdeutility/src/KDEUtilityDialogUI.ui to KDEUtilityDialogUI.py /usr/bin/pyuic -o /var/tmp/package-pytdeextensions/opt/trinity/share/apps/pytdeextensions/app_templates/kdeutility/src/KDEUtilityDialogUI.py.bak /var/tmp/package-pytdeextensions/opt/trinity/share/apps/pytdeextensions/app_templates/kdeutility/src/KDEUtilityDialogUI.ui /usr/bin/pyuic: symbol lookup error: /opt/trinity/lib/libtdecore.so.4: undefined symbol: _ZN7KLocaleD1Ev error: command '/usr/bin/pyuic' failed with exit status 127 Any ideas? Thanks. Darrell

12 years, 7 months

Bug 1063: glib upstream changes to header inclusion (with patch)

by David C. Rankin

Tim, All, Upsteam glib changes have resulted in build failures giving the message: #error "Only <glib.h> can be included directly." The simply changes required mean exactly what the error says "Only <glib.h> can be included directly". What that means to us is that all header files that include reference to old glib headers in the form #include <glib/_whatever_.h> must simply be rewritten as: #include <glib.h> Here is the first patch for gtk-qt-engine. I opened bug http://bugs.pearsoncomputing.net/show_bug.cgi?id=1063 to track and collect patches for the apps that Darrell or Tim can then push after they are signed off on. gtk-qt-engine: --- gtk-qt-engine/src/qt_theme_draw.c +++ gtk-qt-engine/src/qt_theme_draw.c 2012-06-22 14:02:18.691510787 -0500 @@ -3,7 +3,7 @@ #include <gtk/gtkprogressbar.h> #include <gdk/gdk.h> #include <gtk/gtk.h> -#include <glib/glist.h> +#include <glib.h> #ifdef HAVE_BONOBO #include <libbonobo.h> We will want to add preprocessor directives on glib version as well to prevent borking builds on older glib. Also, what about a global fix with sed? -- David C. Rankin, J.D.,P.E.

12 years, 7 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels