Some time ago I tested LibreOffice with TDE integration as available in LibreOffice-tde PPA on the build-farm.
I tested version 4.0.3-14 on Debian Wheezy i386 and was very unuseable. On the File/Open nothing happened. On the File/Save as occurred freezing LibreOffice. I was forced to upgrade to LibreOffice from wheezy- backports (4.1.2-2~bpo70+1 without TDE integration).
Then I tested version 4.0.2-0ubuntu4 on Ubuntu Saucy amd64 and there everything worked smoothly.
Seems we should do some testing. The link above is about KDE4 but perhaps similar patching is needed for Trinity. To my understanding there are two patches. One that affects dialog speed and another that affects spreadsheets.
How long did compiling take on the build farm?
Darrell
On Saturday 28 of December 2013 15:48:56 Darrell Anderson wrote:
Some time ago I tested LibreOffice with TDE integration as available in LibreOffice-tde PPA on the build-farm.
I tested version 4.0.3-14 on Debian Wheezy i386 and was very unuseable. On the File/Open nothing happened. On the File/Save as occurred freezing LibreOffice. I was forced to upgrade to LibreOffice from wheezy- backports (4.1.2-2~bpo70+1 without TDE integration).
Then I tested version 4.0.2-0ubuntu4 on Ubuntu Saucy amd64 and there everything worked smoothly.
Seems we should do some testing. The link above is about KDE4 but perhaps similar patching is needed for Trinity. To my understanding there are two patches. One that affects dialog speed and another that affects spreadsheets.
How long did compiling take on the build farm?
Darrell
Each distribution each platform takes about 4.5 hours. Except armel, where it takes about a month ;)
Slavek --
On Sat, 28 Dec 2013 16:06:28 +0100 Slávek Banko slavek.banko@axis.cz wrote:
Except armel, where it takes about a month ;)
I've been wondering for a while now why the armel builds take so long—are they actually being done on a system with that type of CPU rather than cross-compiled on a faster machine, or is it something inherant in the compilation itself?
E. Liddell
On Sat, 28 Dec 2013 16:06:28 +0100 Slávek Banko slavek.banko@axis.cz wrote:
Except armel, where it takes about a month ;)
I've been wondering for a while now why the armel builds take so longâare they actually being done on a system with that type of CPU rather than cross-compiled on a faster machine, or is it something inherant in the compilation itself?
E. Liddell
For a long time they were being done on a powerful Opteron server via qemu. Yesterday I switched the armel builds to a native 1.7GHz builder based on my success earlier this month with the same hardware and the armhf builds. The armel builds are now running at a much higher rate.
Tim
Dne so 28. prosince 2013 Timothy Pearson napsal(a):
On Sat, 28 Dec 2013 16:06:28 +0100
Slávek Banko slavek.banko@axis.cz wrote:
Except armel, where it takes about a month ;)
I've been wondering for a while now why the armel builds take so longâare they actually being done on a system with that type of CPU rather than cross-compiled on a faster machine, or is it something inherant in the compilation itself?
E. Liddell
For a long time they were being done on a powerful Opteron server via qemu. Yesterday I switched the armel builds to a native 1.7GHz builder based on my success earlier this month with the same hardware and the armhf builds. The armel builds are now running at a much higher rate.
Tim
This change was absolutely perfect! Now builds running much faster than before. This significantly reduces the time for a complete rebuild => hence the period from tag final sources to release.
Tim, many thanks for that.
Slavek --
-
Darrell Anderson -
E. Liddell -
Slávek Banko -
Timothy Pearson