SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just tried running the SlackBuild script for LibreOffice by Christoph Willing off of Sbo on my slackware -current machine, ...
In general, I'm not tracking -current for the SlackBuild at SBo (14.2 only). However I have occasionally provided some updates to ponce's -current repo so that's the place to go for more recent versions of LO (although certainly not the very latest at the moment).
In general, I'm not tracking -current for the SlackBuild at SBo (14.2 only). However I have occasionally provided some updates to ponce's -current repo so that's the place to go for more recent versions of LO (although certainly not the very latest at the moment).
chris
Thanks, from what you know about the SlackBuild given that you wrote it, do you know what sorts of things would stop a 14.2 version working on -current? Because so far, I've been using mostly 14.2 slackbuilds on -current and this is the first one that hasn't worked flawlessly. If you're not sure about LO specifically, any idea for slackbuilds in general? I'm still a newbie to this all so I'm just curious
Thanks, from what you know about the SlackBuild given that you wrote it, do you know what sorts of things would stop a 14.2 version working on -current? Because so far, I've been using mostly 14.2 slackbuilds on -current and this is the first one that hasn't worked flawlessly. If you're not sure about LO specifically, any idea for slackbuilds in general? I'm still a newbie to this all so I'm just curious
LO has a myriad of library and compiler dependencies and many of the changes in newer versions of them (as updated in -current) require changes in LO that now prevent it building with the older libraries in 14.2. While many SlackBuilds at SBo will also work on -current, many also will not work, hence the effort at ponce's repo to track SlackBuild changes required for -current.
LO has a myriad of library and compiler dependencies and many of the changes in newer versions of them (as updated in -current) require changes in LO that now prevent it building with the older libraries in 14.2. While many SlackBuilds at SBo will also work on -current, many also will not work, hence the effort at ponce's repo to track SlackBuild changes required for -current.
The Document Foundation recently released version 7.0.0 of their Libre Office suite of applications. The packages for Slackware-current can be found in my repository. But the situation for Slackware 14.2 used to be different - I got stuck after LibreOffice 6.2 because the newer source releases (6.3 and onwards) require versions of system software that our stable Slackware 14.2 platform does not offer.
From time to time during the last year, when there was time and the build box was not compiling packages, I messed around with the libreoffice.SlackBuild script in futile attempts to compile recent versions of LibreOffice on Slackware 14.2. I failed all the time.
Until last week. After I had uploaded the new KDE Plasma5 packages to 'ktown', I had an epiphany and decided to use a new approach. What I did was: question all the historic stuff in the SlackBuild script that got added whenever I needed to work around compilation failures; and accept that the compilation needs newer versions of software than Slackware 14.2 offers. The first statement meant that I disabled patches and variable declarations that messed with compiler and linker; and for the second statement I stuck to a single guideline: the end product, if I were able to compile a package successfully, has to run out of the box on Slackware 14.2 without the need to update any of the core Slackware packages.
So I ended with a script that only has two new compile-time requirements: use the 'unsupported' gcc 9.2.0 compilers instead of Slackware's ageing gcc-5.5.0. And update gperf to the version you find in Slackware-current. The rest of the required supporting libraries will be compiled into LibreOffice automatically. And this time, the LibreOffice sources compiled without errors.
The resulting binaries would however fail to run on a regular Slackware 14.2 (with the stock versions of gcc and gperf packages) because of missing symbols in the dynamically linked system libraries.
I managed to get around that issue, by adding the two runtime support libraries that come with gcc-9.2.0 (libgcc_s.so.1 and libstdc++.so.6) into the 'program' directory of LibreOffice. Those libraries contain the symbols LibreOffice is looking for; a simple runtime dependency on gcc.
By the way: you cannot expect everybody to install a set of compilers just to run programs, Slackware solves this dilemma by adding the GCC runtime libraries to the 'aaa_elflibs' package which is usually one of the first packages to get installed on a new system.
That worked! LibreOffice 6.4.5 for Slackware 14.2 is now available in my package repository. And I even built LibreOffice 7.0.0 in the same manner. I stuck with 6.4.5 because I want people to be able to use a stable and well-established version of an office suite on the stable Slackware platform. The more experimental 7.0.0 release is for Slackware-current.
Guess what! Today, just when I uploaded the 6.4.5 packages I noticed that the release of LibreOffice 6.4.6 has been announced (and in October we'll see the final release in the 6.4 cycle - being 6.4.7).
I will try to find some time to compile those fresh tarballs; but first I do like feedback about the new 6.4.5 packages that are now downloadable for Slackware 14.2.
Get the packages - as usual - from my own server or one of its mirrors; https://slackware.nl/people/alien/sl...s/libreoffice/ (rsync://slackware.nl/mirrors/people/alien/slackbuilds/libreoffice/) or https://slackware.uk/people/alien/sl...s/libreoffice/ (rsync://slackware.uk/people/alien/slackbuilds/libreoffice/)
Enjoy! Eric
Could anyone tell me roughly how much space a default install of the LibreOffice package with Java support takes up on a system? Trying to install it, it tells me it runs out of space halfway through the build/install process.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 919
Rep:
Quote:
Originally Posted by burning
Could anyone tell me roughly how much space a default install of the LibreOffice package with Java support takes up on a system? Trying to install it, it tells me it runs out of space halfway through the build/install process.
I was trying to build LibreOffice (alienBob's 6.2.8 script) in a 14.2 VirtualBox vm with 2GB ram and 30GB disk (and four cores), didn't build.
With double ram and disk, and eight cores, it took more than 6 hours to build.
I don't know if it was with java support but one of deps to build is java installed.
I was trying to build LibreOffice (alienBob's 6.2.8 script) in a 14.2 VirtualBox vm with 2GB ram and 30GB disk (and four cores), didn't build.
With double ram and disk, and eight cores, it took more than 6 hours to build.
I don't know if it was with java support but one of deps to build is java installed.
Just asking 'cause I have about 3Gb of space left in my root partition and so I'm guessing LibreOffice must somehow be in excess of 3Gb. Trying to figure out how much space I should make before trying to run his script again
Just asking 'cause I have about 3Gb of space left in my root partition and so I'm guessing LibreOffice must somehow be in excess of 3Gb. Trying to figure out how much space I should make before trying to run his script again
Oh I can make the space. I have some unallocated free space in a partition I'm saving for a second OS. Trying to keep the amount of space I steal from it to a minimum though
Any idea how many Gigabytes LO takes up once it's installed?
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 919
Rep:
Quote:
Originally Posted by burning
Oh I can make the space. I have some unallocated free space in a partition I'm saving for a second OS. Trying to keep the amount of space I steal from it to a minimum though
Any idea how many Gigabytes LO takes up once it's installed?
slackpkg says 700MB for LO 7.0
Code:
slackpkg info libreoffice
NOTICE: pkglist is older than 24h; you are encouraged to re-run 'slackpkg update'
PACKAGE NAME: libreoffice-7.0.0-x86_64-1alien.txz
PACKAGE LOCATION: ./libreoffice
PACKAGE SIZE (compressed): 161712 K
PACKAGE SIZE (uncompressed): 704510 K
slackpkg info libreoffice
NOTICE: pkglist is older than 24h; you are encouraged to re-run 'slackpkg update'
PACKAGE NAME: libreoffice-7.0.0-x86_64-1alien.txz
PACKAGE LOCATION: ./libreoffice
PACKAGE SIZE (compressed): 161712 K
PACKAGE SIZE (uncompressed): 704510 K
Ah, thanks. I didn't know the info files listed the size of the package but now that I think about it, really makes sense that it does. I wonder what made me run out of space then.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.