after today's upgrade libboost_locale.so.1.68.0 to libboost_locale.so.1.69.0
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.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Rep:
after today's upgrade libboost_locale.so.1.68.0 to libboost_locale.so.1.69.0
.. libreoffice refuses to load with the error (Slackware-current/Plasma 5/Alien)
Quote:
/usr/lib64/libreoffice/program/soffice.bin: error while loading shared libraries: libboost_locale.so.1.68.0: cannot open shared object file: No such file or directory
The basic solution is that libreoffice needs to be recompiled, I would suggest checking AlienBob's blog for updates. He may already be aware it needs to be rebuilt and has not yet had the time.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Original Poster
Rep:
thank you both,
I am not worried about the issue. I always test each update in VM Slackware, if this will get somehow broken, it does not affect my working system.
Just wanted to let users know that maybe they should hold off the update until office package (and anything that requires boot) gets recompiled.
Those who use -current should already know, that an update to boost will require rebuilds of dependent packages. This is why those who use -current must read and understand the change log. The biggest clue in the 'Fri Dec 14 18:59:34 UTC 2018' change log is 'Shared library .so-version bump.' I never update, with out first checking the change log.
I tried rebuilding Libreoffice using Eric's script but after quite some time it failed citing missing files at line such and such in a script. I deleted without noting specifics. I'll wait until he rebuilds.
Edit:
: Setting Root Module: gid_Module_Root
: Using spellchecker file: /tmp/build/tmp-libreoffice/libreoffice-6.1.3.2/setup_native/source/packinfo/spellchecker_selection.txt
: Collected spellchecker languages for spellchecker: EMPTY,af,an,ar,be,bg,bn,bo,br,bs,ca,cs,da,de,el,en,es,et,fr,gl,he,hi,hr,hu,id,is,it,lt,lv,nl,no,oc,p l,pt-BR,pt-PT,ro,ru,si,sk,sl,sr,sv,te,th,uk,vi,zu
:
: *****************************************************************
: ERROR: ERROR: Missing files at /tmp/build/tmp-libreoffice/libreoffice-6.1.3.2/solenv/bin/modules/installer/scriptitems.pm line 1212.
: *****************************************************************
Sat Dec 15 12:55:29 2018 (00:03 min.)
Failed to install: No such file or directory at /tmp/build/tmp-libreoffice/libreoffice-6.1.3.2/solenv/bin/ooinstall line 91.
make: *** [Makefile:340: install] Error 2
Installing XML files because 'make distro-pack-install' fails to do so...
mv: cannot stat '/tmp/build/package-libreoffice/usr/lib64/libreoffice/sdk/classes': No such file or directory
./libreoffice.SlackBuild FAILED at line 1390
waiting for the update is always a good option. Perhaps that is why he waits, and others too, before they update, to get the updates to update what they got a update.
How many updates can an update date, if an update could update date?
All of the updates an update can update, if an update could update date.
That is how many updates an update would update, if an update could update date.
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Rep:
a request to Alien Bob:
Couldn't it be possible to have as 'icu4c-compat' a 'boost-compat' package to solve that kind of breakage each time icu4c, boost and other package seed the panic?
Couldn't it be possible to have as 'icu4c-compat' a 'boost-compat' package to solve that kind of breakage each time icu4c, boost and other package seed the panic?
Yes that one would already be underway, if only I did not have to drive out to the supermarket to get food.
I tried rebuilding Libreoffice using Eric's script but after quite some time it failed citing missing files at line such and such in a script. I deleted without noting specifics. I'll wait until he rebuilds.
LibreOffice needs a patch if you want to compile against boost-1.69.0.
Be patient, I am getting there. In the meantime look in my repo for a new "boost-compat" package which should appear soon.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Rep:
Quote:
Originally Posted by Alien Bob
LibreOffice needs a patch if you want to compile against boost-1.69.0.
Be patient, I am getting there. In the meantime look in my repo for a new "boost-compat" package which should appear soon.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Original Poster
Rep:
Quote:
Originally Posted by Alien Bob
LibreOffice needs a patch if you want to compile against boost-1.69.0.
Be patient, I am getting there. In the meantime look in my repo for a new "boost-compat" package which should appear soon.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.