tde-devels February 2014

devels@trinitydesktop.org

20 participants
243 discussions

Re: [trinity-devel] undefined symbols in all builds
by Darrell Anderson 10 Feb '14

10 Feb '14

>On Debian and Ubuntu are no apparent problems during build. Commit >2ee14b64 caused FTBFS in tqt3 and this was resolved in commit >dab0c5cd. No other problems have not noticed. Perhaps we should change the name of the project to the Debian Desktop Environment. Darrell

2 1

Re: [trinity-devel] SOLVED!!! - tdeutils superkaramba FTBFS python2/python3 -- patchavail
by Darrell Anderson 10 Feb '14

10 Feb '14

> That's it. Then it builds on bleeding-edge arch without issue. >Darrell, will >you try this patch and confirm that it works fine with python2. >Then let's get a >few more eyes on it and if no objections, push it. > >The patch is included below. I don't have tme to test this. The bug report will have to do. Darrell

1 0

Re: [trinity-devel] Default Doc Install Locations (some strays)
by Darrell Anderson 10 Feb '14

10 Feb '14

> I think these are a couple of stray doc packages, I think the >help files are >in the correct spots, but these stray docs ended up in random >locations: > >22:47 valhalla:~> l1 /opt/trinity/share/doc/ > kbfx > ksquirrel-libs > tde >22:48 valhalla:~> l1 /opt/trinity/share/doc/tde/ > HTML >22:48 valhalla:~> l1 /opt/trinity/share/doc/tde/HTML/ > <snip> > kdiff3 > > The ksquirrel-libs docs may be the whole doc package, but the >others have doc >generation scripts and AUTHOR/HACKING type file. What do you >suggest? Delete >them during packaging? Some developers have egos that simply can't be stroked. Their package is THE package. Do what you want with the files. Darrell

1 0

Re: [trinity-devel] undefined symbols in all builds
by Darrell Anderson 10 Feb '14

10 Feb '14

>Can I pose a question? > > Why are we looking to add Q_EXPORT calls, and we are we making >commits >containing them until they are tested? Please reverse commits dab0c5cd and 2ee14b64 until they are fully tested and debugged. Darrell

2 1

Re: [trinity-devel] undefined symbols in all builds
by Darrell Anderson 10 Feb '14

10 Feb '14

>Any other methods? >You can send a list? No, because each time I copy what you did in your patch to add Q_EXPORT to a different location, yet another new 'undefined symbols' message appears. The messages do not all appear at the same time in one nice dump. Reversing commit 2ee14b64 resolves the problem. Darrell

3 3

Confirm size of python-trinity package
by David C. Rankin 10 Feb '14

10 Feb '14

Darrell, Slavek, Can you confirm the size of the python-trinity package you are building. I built python-trinity last night for the first time and I was bewildered by the fact it took 20 minutes to build and resulted in a package that was over 20M. 10:51 phoinix:/dat_e/tde/pkg> l i686/tde-python-trinity-R14preRC1-1-i686.pkg.tar.xz -rw-r--r-- 2442140 Feb 10 04:01 i686/tde-python-trinity-R14preRC1-1-i686.pkg.tar.xz During the build, there was a wholesale lack of any build output. At times I thought the build was hung, but checking with top, the build was cranking away with cclplus pegging one of the cores at 100%. I don't know if a library path change is needed or whether the build just spins it wheels looking through /lib, but something seems like it is caught in a race condition. There is also a hardcoded search path for KDE353 or kde353 stuck in the build somewhere. What are others seeing? -- David C. Rankin, J.D.,P.E.

1 0

Why the net htdig dependency in tdebase?
by David C. Rankin 10 Feb '14

10 Feb '14

All, Last night I kicked off a build and the build failed at tdebase due to missing htdig dependency. Simple fix, just added htdig as a dependency, but why the new requirement? -- David C. Rankin, J.D.,P.E.

2 2

Re: [trinity-devel] undefined symbols in all builds
by Darrell Anderson 10 Feb '14

10 Feb '14

>I think, this relates with commit 2ee14b64. >Try attached patch. Doesn't help. I still get a slew of the same type of messages. Darrell

2 1

Default Doc Install Locations (some strays)
by David C. Rankin 10 Feb '14

10 Feb '14

Darrell, I think these are a couple of stray doc packages, I think the help files are in the correct spots, but these stray docs ended up in random locations: 22:47 valhalla:~> l1 /opt/trinity/share/doc/ kbfx ksquirrel-libs tde 22:48 valhalla:~> l1 /opt/trinity/share/doc/tde/ HTML 22:48 valhalla:~> l1 /opt/trinity/share/doc/tde/HTML/ <snip> kdiff3 The ksquirrel-libs docs may be the whole doc package, but the others have doc generation scripts and AUTHOR/HACKING type file. What do you suggest? Delete them during packaging? -- David C. Rankin, J.D.,P.E.

1 0

libraries - build order/dependencies
by David C. Rankin 10 Feb '14

10 Feb '14

All, Does anyone have a list of what the dependencies/build-order is for all of the tde/main/libraries/x files are? I have been successfully building in this order: <snip> 'tdelibs' 'tdebase' 'libraries/libksquirrel' 'libraries/libkdcraw' 'libraries/libkexiv2' 'libraries/libkipi' 'libraries/kipi-plugins' 'libraries/libtdeldap' 'libraries/libtqt-perl' 'libraries/mlt' 'libraries/mlt++' I would like to turn this around and build all dependencies, then libraries, the tde: "dependencies/$useqt" 'dependencies/tqtinterface' 'dependencies/arts' 'dependencies/dbus-tqt' 'dependencies/dbus-1-tqt' 'dependencies/tqca-tls' 'dependencies/libart-lgpl' 'dependencies/avahi-tqt' 'dependencies/libcaldav' 'dependencies/libcarddav' 'dependencies/sip4-tqt' 'dependencies/python-tqt' 'dependencies/tqscintilla' 'libraries/libksquirrel' 'libraries/libkdcraw' 'libraries/libkexiv2' 'libraries/libkipi' 'libraries/kipi-plugins' 'libraries/libtdeldap' 'libraries/libtqt-perl' 'tdelibs' 'tdebase' However, I have 'tdebase' listed as a dependency for 'libraries/libksquirrel'. Can anyone confirm this is required, or do I just have a spurious 'tdebase' stuck in the dependency list? -- David C. Rankin, J.D.,P.E.

1 0

← Newer
1
...
10
11
12
13
14
15
16
...
25
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels February 2014