alienbob's libre office/slack64 current

chris.willing · 09-10-2016, 06:45 AM

Quote:

Originally Posted by mats_b_tegner

LibreOffice Calc is dependent on Boost. The repackaged version uses a bundled version. AlienBob's uses the system version. BLFS has some info regarding it:
http://www.linuxfromscratch.org/blfs...breoffice.html

The build from source SlackBuild from SBo also uses:

Code:

--with-system-boost \

and localc seems to run without any problem so I don't think the boost version is the problem in this case.

chris

Skaendo · 09-10-2016, 07:15 AM

Quote:

Originally Posted by phenixia2003

Hello,

Just for fun, you can get it to work as below :

--
SeB

Nice hack. Works for me.

I tried compiling LibreOffice from Eric's repo, three times, but he has it kludged together in some way that I can't figure out. Well I probably could, but just don't want to spend that much time on it.

mats_b_tegner · 09-10-2016, 08:58 AM

Quote:

Originally Posted by chris.willing

The build from source SlackBuild from SBo also uses:

Code:

--with-system-boost \

and localc seems to run without any problem so I don't think the boost version is the problem in this case.

chris

I haven't built LibreOffice from source. I can only confirm that AlienBob's version currently only works with Boost version 1.59.0.

chris.willing · 09-10-2016, 09:13 AM

Quote:

Originally Posted by mats_b_tegner

I haven't built LibreOffice from source. I can only confirm that AlienBob's version currently only works with Boost version 1.59.0.

Well boost 1.59.0 happens to be the version supplied in stock SL-14.2. AlienBob's SlackBuild at the moment uses boost 1.60.0 and is configured

Code:

--without-system-boost

i.e. does not use the system boost (as was previously suggested).

chris

mats_b_tegner · 09-10-2016, 11:30 AM

Quote:

Originally Posted by chris.willing

Well boost 1.59.0 happens to be the version supplied in stock SL-14.2. AlienBob's SlackBuild at the moment uses boost 1.60.0 and is configured

Code:

--without-system-boost

i.e. does not use the system boost (as was previously suggested).

chris

Okay, Eric told me that he doesn't have time to rebuild LO for -current at the moment since it takes two days. But since it's possible to install boost 1.59.0 in /opt or use the repackaged RPM version from SlackBuilds.org I'm happy.

Alien Bob · 09-10-2016, 02:47 PM

The SlackBuild script uses "--without-system-boost" but I suspect that the build process links to system boost libraries nevertheless.
Applying "ldd" shows that a couple of the LibreOffice libraries do in fact link to the 1.59.0 version of boost libraries.

trollog · 09-10-2016, 05:59 PM

started a recompile yesterday, of current.

whoa is that a long compile.

I'm about 24 hours in. I'll keep you posted as things progress.

The python angle seemed like BS

The boost angle seems totally plausible.

Time will tell.

One hell of a package to compile.

Ah, the hours of time AB's LO package saved me all these years.

I never knew...

.

Alien Bob · 09-10-2016, 06:01 PM

There will be a LibreOffice 5.2.1 package for Slackware-current after the weekend. Indeed, it takes long to compile.

trollog · 09-13-2016, 03:52 AM

Both my compiles- one using your pre-sept 10 build scripts, and the other using LO source from upstream bombed at about 30 hours in.
(ungodly long compile times there..)

I saw your new LO packages built over the weekend, which made my efforts redundant in the end.
Your packages are now installed and working fine on my current_64 computers.

But still- my compiles bombed, yours were successful. What changes exactly were made never really got
mentioned or explained in great detail. Would it be as simple as diff'ing the pre Sept 10 libreoffice.Slackbuild file? How would I go back
and see exactly what you changed? Which (build)files would I grep? Just point me in a direction. I'll make the effort to understand
what's in the files themselves. No hand-holding needed.

If you are going to have less time to devote for personal reasons which are perfectly reasonable, then all of us who
have come to rely on your packages are going to need to become a lot more self-reliant. We all got lucky this time because
of the quick turnaround time from you (thank you, btw). But it makes me think we also collectively dodged a bullet here and may not
get so lucky the next time.

In some respect you have spoiled us with some really great builds over the years. The good thing is they "just work"
when installed. The bad thing, for me personally, is that I have let my own skills atrophy a bit because your builds were
just so convenient. I take the lazy way and install the packages because I trust them and it's easy.

LO is kind of a funny case. I build many smaller relatively fast compiling things myself (electrix pdf viewer- always very "breaky" under /current) without
even bothering to make them into proper packages. Arduino has wild quality issues, changes & release schedules so I don't even bother making
proper packages. Just not worth the time for a piece of software that is "hard beta" quality & changing so fast. Electrix has lib issues in /current and
often breaks after upgrades, but whatever, it's trivial to compile and compiles fast. Ditto for gtk-gnutella.
LO has always been a real community service provided by you, due to the complex dependencies & long compile times.

I'm just thinking ahead to the days when you are not here to put in the extra overtime to bail all our collective butts out of the sling
when a useful, but intricate & fussy package breaks again, as is normal in the cycle of development of a living evolving software package.

.

Alien Bob · 09-13-2016, 10:11 AM

Mostly a LibreOffice compilation fails when there's not enough RAM. There is no significant difference between the SlackBuild scripts for LO 5.2.0 and 5.2.1:

Code:

--- /home/slackbuilds/libreoffice/build/libreoffice.SlackBuild	2016/08/04 07:26:21	1.71
+++ /home/slackbuilds/libreoffice/build/libreoffice.SlackBuild	2016/09/10 11:09:27
@@ -1,5 +1,5 @@
 #!/bin/sh
-# $Id: libreoffice.SlackBuild,v 1.71 2016/08/04 07:26:21 root Exp $
+# $Id: libreoffice.SlackBuild,v 1.72 2016/09/10 11:09:24 root Exp root $
 # Copyright 2010, 2011, 2012, 2013, 2014, 2015, 2016  Eric Hameleers, Eindhoven, NL
 # All rights reserved.
 #
@@ -227,6 +227,8 @@
 #             * Update.
 # 5.2.0-1:    03/aug/2016 by Eric Hameleers <alien@slackware.com>
 #             * First release of the 5.2 series.
+# 5.2.1-1:    10/sep/2016 by Eric Hameleers <alien@slackware.com>
+#             * Update.
 #
 # Run 'sh libreoffice.SlackBuild' to build a Slackware package.
 # The package (.txz) and .txt file as well as build logs are created in /tmp .
@@ -257,8 +259,8 @@
 #SRCVER=${SRCVER:-5.0.0.2git}
 #SRCVER=${SRCVER:-5.0.0.2}
 
-SRCVER=${SRCVER:-5.2.0}
-SUBVER=".4"
+SRCVER=${SRCVER:-5.2.1}
+SUBVER=".2"
 PKG_SUBVER=""
 
 # How many tarballs does this release consist of:
@@ -383,7 +385,7 @@
 #
 
 # --- Start of section generated by gensrc.sh ---
-# External sources for libreoffice-5.2.0.4
+# External sources for libreoffice-5.2.1.2
 
 SOURCE[6]="$SRCDIR/sources/185d60944ea767075d27247c3162b3bc-unowinreg.dll"
 SRCURL[6]="http://dev-www.libreoffice.org/extern/185d60944ea767075d27247c3162b3bc-unowinreg.dll"
@@ -621,8 +623,8 @@
 SRCURL[64]="http://dev-www.libreoffice.org/src/libjpeg-turbo-1.4.2.tar.gz"
 GITURI[64]=""
 
-SOURCE[65]="$SRCDIR/sources/language-subtag-registry-2016-02-10.tar.bz2"
-SRCURL[65]="http://dev-www.libreoffice.org/src/language-subtag-registry-2016-02-10.tar.bz2"
+SOURCE[65]="$SRCDIR/sources/language-subtag-registry-2016-07-19.tar.bz2"
+SRCURL[65]="http://dev-www.libreoffice.org/src/language-subtag-registry-2016-07-19.tar.bz2"
 GITURI[65]=""
 
 SOURCE[66]="$SRCDIR/sources/b63e6340a02ff1cacfeadb2c42286161-JLanguageTool-1.7.0.tar.bz2"
@@ -737,12 +739,12 @@
 SRCURL[93]="http://dev-www.libreoffice.org/src/c63f411b3ad147db2bcce1bf262a0e02-pixman-0.24.4.tar.bz2"
 GITURI[93]=""
 
-SOURCE[94]="$SRCDIR/sources/libpng-1.6.19.tar.gz"
-SRCURL[94]="http://dev-www.libreoffice.org/src/libpng-1.6.19.tar.gz"
+SOURCE[94]="$SRCDIR/sources/libpng-1.6.24.tar.gz"
+SRCURL[94]="http://dev-www.libreoffice.org/src/libpng-1.6.24.tar.gz"
 GITURI[94]=""
 
-SOURCE[95]="$SRCDIR/sources/poppler-0.26.4.tar.gz"
-SRCURL[95]="http://dev-www.libreoffice.org/src/poppler-0.26.4.tar.gz"
+SOURCE[95]="$SRCDIR/sources/poppler-0.46.0.tar.bz2"
+SRCURL[95]="http://dev-www.libreoffice.org/src/poppler-0.46.0.tar.bz2"
 GITURI[95]=""
 
 SOURCE[96]="$SRCDIR/sources/c0b4799ea9850eae3ead14f0a60e9418-postgresql-9.2.1.tar.bz2"

trollog · 09-13-2016, 03:54 PM

would you consider 4GB RAM too little?
1 Tb hard drive
amd 1800 dual core

It's a lenovo thats 2.5 yrs old.
running /current_64

No other user processes going on during compile.
(used my laptop for a few days for everyday activities)
Not because of memory concerns but because using a
computer with the processor pegged is not a pleasant experience.

If 4GB is too little RAM these days then I
need to upgrade.

Skaendo · 09-13-2016, 04:00 PM

Quote:

Originally Posted by trollog

would you consider 4GB RAM too little?
1 Tb hard drive
amd 1800 dual core

It's a lenovo thats 2.5 yrs old.
running /current_64

No other user processes going on during compile.
(used my laptop for a few days for everyday activities)

If 4GB is too little RAM these days then I
need to upgrade.

I'm in the same boat as you,
current-x64, Core 2 Duo @ 2 GHz & 4 GB RAM.

For the everyday stuff it's fine. Compiling webkitgtk3 takes about 6 hours or so.

Unfortunately, This is the most RAM that that rig will take. I have heard that I can squeeze 2 more in there running a 2 GB stick and a 4 GB stick, but have yet been brave enough to try it.

trollog · 09-13-2016, 04:10 PM

and 4gb ain't enough anymore these days,

that would certainly explain some things.

Otherwise, the causes for the build bombing are cryptic

rkelsen · 09-13-2016, 06:57 PM

Quote:

Originally Posted by trollog

and 4gb ain't enough anymore these days,

that would certainly explain some things.

Otherwise, the causes for the build bombing are cryptic

The big lesson here is don't run -current if you expect things to work properly.

It's not like Debian's -testing branch. The -current branch should be considered pre-alpha. It is unstable, which means that things will break. And Murphy's law dictates that they'll break whenever it's least convenient for you.

trollog · 09-13-2016, 09:22 PM

I was the first to find/mention an issue with one of the current_64 packages.

I brought the issue to the fore.

That it's an unofficial package is irrelevant.

The issue was addressed & fixed.

Now that's the system & forum working as it should.

That's the big lesson here, not some other.