[SOLVED] AlienBob's LibreOffice 7.2.0 fails to start in Slackware Current after all updates
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.
I don't see rsamurti replying to anything in that thread, so how can you know it's been solved?
Once again, for especially gifted bloggers, I'm trying, the problem was solved by UPDATING the PACKAGE on the website of the PACKAGE itself, download the whole package from https://LibreOffice.org , and don't fuck people's brains.
Once again, for especially gifted bloggers, I'm trying, the problem was solved by UPDATING the PACKAGE on the website of the PACKAGE itself, download the whole package from https://LibreOffice.org , and don't fuck people's brains.
As far as I can see from your other thread Roman, you did not download and install a "package". You downloaded the Libre Office source code, ran something resembling "configure && make && make install" and then started the resulting binary from its local installation path "/usr/local/lib/libreoffice/program/soffice". That is your private binary, it does not help rsamurti a single bit that your locally compiled sources work for you.
As far as I can see from your other thread Roman, you did not download and install a "package". You downloaded the Libre Office source code, ran something resembling "configure && make && make install" and then started the resulting binary from its local installation path "/usr/local/lib/libreoffice/program/soffice". That is your private binary, it does not help rsamurti a single bit that your locally compiled sources work for you.
what well to do , if you package is OUTDATED ?
in LibreOffice.org now was changed build system, it now how like a FreeBSD "make", do get dependencies AUTOMATED from internet.
Compilation was light and easy.
Fri Oct 15 05:34:36 UTC 2021
libreoffice: updated to 7.2.2 for Slackware-current.
You can compile this on Slackware 14.2 yourself with some caveats, see the
header of the libreoffice.SlackBuild.
Fri Oct 15 05:34:36 UTC 2021
libreoffice: updated to 7.2.2 for Slackware-current.
You can compile this on Slackware 14.2 yourself with some caveats, see the
header of the libreoffice.SlackBuild.
Why does a person need a slackbuild, if you just need to go to the calalog and start the assembly, because this slackbuild will lead to an error.
The standard assembly from the package LibreOffice.org itself for the Slackware receives all the necessary automatically !
Why does a person need a slackbuild, if you just need to go to the calalog and start the assembly, because this slackbuild will lead to an error.
The standard assembly from the package LibreOffice.org itself for the Slackware receives all the necessary automatically !
nope
I'm not sure if you really know Alienbob's work ...
Quote:
Why does a person need a slackbuild
probably because the binaries are ready to be installed and with slackpkg+ it takes 20sec to install
mkdir libreoffice
cd libreoffice
wget -c -r -A *.txz -nd -np http://www.slackware.com/~alien/slackbuilds/libreoffice/pkg64/current/
su
installpkg libreoffice*.txz
both, slackpkg+ and sbopkg, is not a clear Slackware way - build pkg from source, also have integrated makepkg Slackware utility.
Code:
bash-5.1# makepkg --help
Usage: makepkg package_name.tgz
(or: package_name.tbz, package_name.tlz, package_name.txz)
Makes a Slackware compatible package containing the contents of the current
and all subdirectories. If symbolic links exist, they will be removed and
an installation script will be made to recreate them later. This script will
be called "install/doinst.sh". You may add any of your own ash-compatible
shell scripts to this file and rebuild the package if you wish.
options: -l, --linkadd y|n (moves symlinks into doinst.sh: recommended)
-p, --prepend (prepend rather than append symlinks to an existing
doinst.sh. Useful to link libraries needed by programs in
the doinst.sh script)
-c, --chown y|n (resets all permissions to root:root 755 - not
generally recommended)
--threads <number> For xz/plzip compressed packages, set the max
number of threads to be used for compression. Only has an
effect on large packages. For plzip, the default is equal to
the number of CPU threads available on the machine. For xz,
the default is equal to 2 (due to commonly occuring memory
related failures when using many threads with multi-threaded
xz compression).
--compress <option> Supply a custom option to the compressor.
This will be used in place of the default, which is: -9
--acls Support storing POSIX ACLs in the package. The resulting
package will not be compatible with pkgtools version < 15.0.
--xattrs Support storing extended attributes in the package. The
resulting package will not be compatible with pkgtools
version < 15.0.
If these options are not set, makepkg will prompt if appropriate.
i show what LibreOffice.org can get direct all dependencies, and build automatically.
./configure
make
make install
is light and very easy today !
but i'm not set branding (name or other), it very easy do set $VALUE
Gives me a selection list to install from.
I select the following:
libreoffice-dict-en-7.2.2-x86_64-1alien
libreoffice-kde-integration-7.2.2-x86_64-1alien
libreoffice-7.2.2-x86_64-1alien
slackpkg is the slackware way, slackpkg+ added third party packages.
Quote:
i show what LibreOffice.org can get direct all dependencies, and build automatically.
./configure
make
make install
With no control over where LibreOffice or what dependencies are installed. Not the Slackware way in my opinion.
That said it's great that it works for you. Perhaps I will experiment this with and see for my self.
Last edited by chrisretusn; 10-16-2021 at 09:35 AM.
I have been following along. I run an up-to-date full install of Slackware64-Current and I just install AlienBob's rebuilt Slackware packages.
I wonder for how long I have missed installing libreoffice-kde-integration. Never knew it was provided, never installed it and everything runs without a problem. It is not on my system presently and there are no plans to install it now or in the future
Last edited by Gordie; 10-16-2021 at 09:23 PM.
Reason: Specify "full install"
There are many tools Eric built that are at your disposal. many things have not caught up to Current but the tools are there.
Eric retired from LQ good and bad thing good is his translation of english seems to be very vulgar at times. Just like Pat's
But the tools are there neither one of them actually write code.
they are good at fixing stuff and that in it's self is a huge art.
Use the tools edit the tools fix the tools.
Grab a copy of his git and do it.
So if you think Pat or Eric write patches and contribute to the software you build show me one.
They are packagers Just like Willy like many other distro people.
They are nothing like SUSE maintainer that maintains ALSA.
There work is to create scripts build packages and hope some Dev does the work.
No more no less.
just good old people trying to make it work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.