tde-devels

devels@trinitydesktop.org

7 participants
3840 discussions

Cross Check on ftbfs packages
by David C. Rankin 22 Jun '12

22 Jun '12

Darrell, On my build tonight (today's source) I have the following build failures: libraries/libksquirrel tdebindings tdegraphics applications/amarok applications/gtk-qt-engine applications/kchmviewer applications/kdmtheme applications/kbfx applications/kima applications/kstreamripper applications/krusader applications/kmplayer applications/kuickshow applications/digikam Could you check to see which you are currently successfully building (post TQt name change). I'll dig into the logs tomorrow, but if it "builds for you", that gives me a reference... :) I'll also look at the graphics issues tomorrow. -- David C. Rankin, J.D.,P.E.

3 8

tdegraphics FTBFS - error: no matching function for call to 'PSOutputDev::PSOutputDev
by David C. Rankin 22 Jun '12

22 Jun '12

Tim, Darrell, Both pre/post TQt3 namechange, I am experiencing tdegraphics build fails due to no matching function for call to 'PSOutputDev::PSOutputDev(const char*, XRef*, Catalog*, NULL, int, int, PSOutMode, int&, int&)'. Does this fall under the "still fixing stuff - wait another week and try again" realm of errors, or is this a separate issue we need to dig into? The full error is: [ 10%] Building CXX object kfile-plugins/dependencies/poppler-tqt/CMakeFiles/poppler-tqt-shared.dir/poppler-document.cc.o cd /build/src/build/kfile-plugins/dependencies/poppler-tqt && /usr/bin/c++ -Dpoppler_tqt_shared_EXPORTS -DHAVE_CONFIG_H -fpermissive -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -I/opt/tqt3/include -I/usr/include/tqt -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -fPIC -I/build/src/build/kfile-plugins/dependencies/poppler-tqt -I/build/src/build -I/opt/trinity/include -I/opt/tqt3/include -I/usr/include/tqt -I/build/src/tdegraphics/kfile-plugins/dependencies/poppler-tqt -I/usr/include/poppler -o CMakeFiles/poppler-tqt-shared.dir/poppler-document.cc.o -c /build/src/tdegraphics/kfile-plugins/dependencies/poppler-tqt/poppler-document.cc /build/src/tdegraphics/kfile-plugins/dependencies/poppler-tqt/poppler-document.cc: In member function 'bool Poppler::Document::print(const TQString&, TQValueList<int>, double, double, int, int, int)': /build/src/tdegraphics/kfile-plugins/dependencies/poppler-tqt/poppler-document.cc:323:167: error: no matching function for call to 'PSOutputDev::PSOutputDev(const char*, XRef*, Catalog*, NULL, int, int, PSOutMode, int&, int&)' /build/src/tdegraphics/kfile-plugins/dependencies/poppler-tqt/poppler-document.cc:323:167: note: candidates are: In file included from /build/src/tdegraphics/kfile-plugins/dependencies/poppler-tqt/poppler-document.cc:28:0: /usr/include/poppler/PSOutputDev.h:108:3: note: PSOutputDev::PSOutputDev(PSOutputFunc, void*, char*, PDFDoc*, int, int, PSOutMode, int, int, GBool, int, int, int, int, GBool, GBool, PSOutCustomCodeCbk, void*) /usr/include/poppler/PSOutputDev.h:108:3: note: no known conversion for argument 1 from 'const char*' to 'PSOutputFunc {aka void (*)(void*, const char*, int)}' /usr/include/poppler/PSOutputDev.h:95:3: note: PSOutputDev::PSOutputDev(const char*, PDFDoc*, char*, int, int, PSOutMode, int, int, GBool, int, int, int, int, GBool, GBool, PSOutCustomCodeCbk, void*) /usr/include/poppler/PSOutputDev.h:95:3: note: no known conversion for argument 2 from 'XRef*' to 'PDFDoc*' /usr/include/poppler/PSOutputDev.h:91:7: note: PSOutputDev::PSOutputDev(const PSOutputDev&) /usr/include/poppler/PSOutputDev.h:91:7: note: candidate expects 1 argument, 9 provided make[2]: *** [kfile-plugins/dependencies/poppler-tqt/CMakeFiles/poppler-tqt-shared.dir/poppler-document.cc.o] Error 1 make[2]: Leaving directory `/build/src/build' make[1]: *** [kfile-plugins/dependencies/poppler-tqt/CMakeFiles/poppler-tqt-shared.dir/all] Error 2 make[1]: Leaving directory `/build/src/build' make: *** [all] Error 2 -- David C. Rankin, J.D.,P.E.

3 8

Incomplete icon theme sets
by Darrell Anderson 22 Jun '12

22 Jun '12

As we continue updating our graphic images with respect to branding issues (thank you!), I have become more aware of how incomplete are the icon theme sets. The crystalsvg set is the default set and even with that set occasionally I find a missing icon of a specific size. The other icon theme sets have many missing icons. I believe the icon display algorithm uses an icon from the selected theme but when an icon is not available to then use one from the default theme crystalsvg. Doable, but I'd like to see us add the missing icons to each theme set. For example, today I was testing my newly added toolbar icons for Ark. When I changed icon themes my konqueror icons looked goofy. I use tree view and tiny icons and there were some missing tiny (16 pixel) icons for the ikon theme. The icon algorithm used larger icons, which did not match the tiny icons. Goofy and kind of amateurish looking. Creating the missing icons was reasonably straightforward using kiconedit and resizing. At the moment all I am asking is reporting. When you see missing icons then drop a note to this mail list. If you are able, possibly create the missing icon. I find I toggle between kiconedit and kolourpaint to create icons. The former is better at resizing and basic pixel-by-pixel changes but the latter has additional paint tools to add missing elements. I always use with the largest icon available to create smaller icons. Or I use karbon or gwenview to load an svgz and then export as a png, which I then load into kiconedit or kolourpaint to resize. I'm somewhat amazed at how incomplete the icon theme sets really are. This is not a critical or urgent request. Just one of those things that if we all are aware then we can continually peck away at the problem. :-) As always, thanks again! Darrell

1 0

koffice - ftbfs - 58 min into build #error "Only <glib.h> can be included directly."
by David C. Rankin 22 Jun '12

22 Jun '12

Darrell, All, Attempting to build koffice last night, I thought it might work. This morning revealed there is still work to be done. 58 minutes into the build, it crashed: libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../.. -I. -I../../../lib/kofficeui -I../../../lib/kofficeui -I../../../lib/kofficecore -I../../../lib/kofficecore -I../../../lib/store -I../../../lib/store -I../../../lib/kwmf -I../../../lib/kwmf -I../../../lib/kopalette -I../../../lib/kopalette -I/usr/include -I/usr/include -I/usr/include/libgsf-1 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/opt/trinity/include -I/opt/tqt3/include -I. -include tqt.h -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -fpermissive -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DHAVE_KNEWSTUFF -MT graphicshandler.lo -MD -MP -MF .deps/graphicshandler.Tpo -c graphicshandler.cpp -fPIC -DPIC -o .libs/graphicshandler.o In file included from /usr/include/wv2/olestream.h:26:0, from graphicshandler.cpp:23: /usr/include/glib-2.0/glib/giochannel.h:28:2: error: #error "Only <glib.h> can be included directly." make[4]: *** [graphicshandler.lo] Error 1 make[4]: Leaving directory `/build/src/koffice/filters/kword/msword' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/build/src/koffice/filters/kword' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/src/koffice/filters' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/build/src/koffice' make: *** [all] Error 2 -- David C. Rankin, J.D.,P.E.

2 2

TQt3 Name Change - Potential Problem - what about apps that Need moc?
by David C. Rankin 21 Jun '12

21 Jun '12

Tim, Darrell, How will the TQt3 executable name change affect packages that look for Qt3 executable to build??? Example 'pinentry' needs qmoc to build with '--enable-pinentry-qt'. Will the name changes from moc or qxx.moc (whatever) to tqxx.moc break these supporting packages? I never would have thought about the supporting packages, but I needed to rebuild pinentry and that provoked the thought. What say the wizards? Will all supporting packages that rely on ..moc need to be hacked to look for ..tqmoc stuff? I have no idea how extensive this list is... Will it even matter or is this just an errant thought? -- David C. Rankin, J.D.,P.E.

5 18

kchmviewer and comic k=>t rename
by Slávek Banko 21 Jun '12

21 Jun '12

Hey. During the cherry picking patches for kchmviewer I noticed one comic / unwanted rename: src/kchmbookmartwindow.cpp. It would probably be a good idea to rename it back (and all references in the Makefile)? Slavek --

2 1

fish/sftp - need to coordinate opening many files over remote link to prevent ssh connection collisions
by David C. Rankin 20 Jun '12

20 Jun '12

All, THis was rather comical. I have a kate session with 100 TDE PKGBUILD scripts as the files within the session. I decided to open a copy from the box at work via sftp and my desktop went nuts. (Connection Closed dialogs _everywhere_) See: http://www.3111skyline.com/dl/dt/trinity/ss/kwrite-100-remote-files.jpg After clicking cancel on all the connection closed dialogs -- all I had to do was select the untitled file and press F5 to refresh the file in the kate session. I think we should put a bit of delay into the fopen calls to insure they are not stepping all over themselves. Anybody else have any ideas to fix this? -- David C. Rankin, J.D.,P.E.

1 0

TQt3 FTBFS - Looks like build scripts need renaming as well
by David C. Rankin 20 Jun '12

20 Jun '12

Darrell, TQt3 fails to build with the following (during packaging). Looks like the build scripts :( ( [ -d styles ] && cd styles ; make -f Makefile install; ) || true make[3]: Entering directory `/build/src/tqt3/plugins/src/styles' make[3]: Nothing to be done for `install'. make[3]: Leaving directory `/build/src/tqt3/plugins/src/styles' make[2]: Leaving directory `/build/src/tqt3/plugins/src' make[1]: Leaving directory `/build/src/tqt3' install: cannot stat 'qmake/qmake': No such file or directory ==> ERROR: A failure occurred in package(). Aborting... I think this is on my end, but all other packagers will have to check their setup as well... -- David C. Rankin, J.D.,P.E.

3 4

Ark Extraction Dialog Broken?
by Darrell Anderson 20 Jun '12

20 Jun '12

I think the Ark extraction dialog is broken. Ark refuses to retain a kdialog size. The dialog always opens too small for me to read the file text box. I have to manually resize every time. Rinse, repeat. Frustrating. Ark does not use a full kdialog. There is no toolbar, hence, no button with my bookmarks. Ark won't retain a dialog history. I have two working directories to which I routinely want to extract files. I want those locations retained in the drop-down history. Each time I open Ark the dialog defaults to $HOME/{$ARCHIVE_NAME} with no history. Sometimes Ark will default to extracting to $HOME/{$PREVIOUS_ARCHIVE_NAME}//{$ARCHIVE_NAME}, which to silly. (Also notice the double slash.) Just to be sure, I created a fresh profile and noticed the same behavior. I can somewhat cheat by manually editing arkrc with the following: [generic] extractionHistory[$e]=/some/directory1,/some/directory2 I don't know why Ark doesn't automatically create that config key. I seem to recall this working at one time in 3.5.10, but I can't get this to work there any more either. This is classic paper cut territory and I'm bleeding. :-) I would be grateful if somebody would confirm this wacky behavior before I write a bug report. Darrell

2 2

Arch update - gcc 4.7.1 hists testing repo, kwrite crash?
by David C. Rankin 20 Jun '12

20 Jun '12

All, Just a quick update. gcc 4.7.1 has it the testing repository for Arch Linux. This will hopefully allow a resolution of what was causing the race condition in tdelibs/tdebase leading to the kwrite crash on line-wrap. However, as is the Arch tradition, the chroot build environment is going though growing pains resulting from the recent updates to the Arch package manager 'pacman'. We will hopefully work though this in the next couple of days and have a new set of packages build on 4.7.1 to test. Nothing like working on the leading (not bleeding) edge :) -- David C. Rankin, J.D.,P.E.

2 12

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels