Alien Bob |
05-18-2020 12:53 AM |
Quote:
Originally Posted by dchmelik
(Post 6124447)
'Still?' Never had it run in Slackware-current. After installing that lately, I built dependencies & Libre Office binaries from source code. It installed. That version didn't run; neither did yours (after upgrading) (when launched in KDE5, icon/taskbar thing starts as if it'll start, then disappears.) I realize I should've said more, but even 'soffice' in xterm does nothing: no output of what it's doing to use for debugging (even for five or 10 minutes... though unlike from KDE start menu, doesn't exit immediately; I have to ^C to return to prompt in xterm.)
|
The fact that the official LIbreOffice binaries won't run, nor my Slackware-compiled packages, nor the ones you compiled yourself... it must be something with your local OS installation (missing/outdated/co-installed software) or your particular PC hardware possibly combined with graphics drivers.
Quote:
Of course, sbopkg lets you build/install either from source code or a prebuilt binary, and I have no idea which yours is like (of course sometimes being different) or dependencies are (for any of your packages.)
|
The libreoffice packages in my repository are compiled on Slackware, by me.
For all my packages, there's a SlackBuild script available which has build-time and run-time dependendies listed in the script's header part. And there's a slack-required file with run-time dependencies as well which will get embedded into the package so that tools like slapt-get can do their own dependency resolving.
|