[SOLVED] Boost-1.6.7

cwizardone · 08-14-2018, 10:55 PM

It appears LibreOffice and the latest boost-1.6.8 update in -current do not get along.
I've been searching for a .txz of boost-1.6.7, but can't locate it. Does anyone know where I might download a copy?
Many thanks.

Darth Vader · 08-14-2018, 11:09 PM

http://slackmirror.cbpf.br/pub/slack...are64-current/

The magic mirror which keep all packages since Ice Age. I needed it too some time ago, for an older linux-firmware.

The_Dark_Passenger · 08-15-2018, 03:27 AM

I updated my -current installation which included boost 1.6.8. Libreoffice version 6.0.5 also stopped working for me. However, upgrading to 6.1 using the Slackbuild here, https://slackbuilds.org/repository/1...e/libreoffice/ fixed the issue. I am now running Libreoffice 6.1 without any issues on my Slackware64 -current installation.

chrisVV · 08-15-2018, 03:45 AM

Quote:

Originally Posted by cwizardone

It appears LibreOffice and the latest boost-1.6.8 update in -current do not get along.
I've been searching for a .txz of boost-1.6.7, but can't locate it. Does anyone know where I might download a copy?
Many thanks.

Not to answer your question, but to run LibreOffice on slackware-current I have started using the app-image version available at https://www.libreoffice.org/download/appimage/ . That supplies its own version of boost and numerous other libraries. You need to make the file executable with chmod +x when you have downloaded it.

It seems to work OK. I am not certain what the difference between "fresh" and "still" is, but in any event I run the "fresh" version.

paolo27957 · 08-15-2018, 03:54 AM

An alternative method is the usual dirty hack:

Quote:

ln -s /usr/lib64/libboost_system.so.1.68.0 /usr/lib64/libboost_system.so.1.67.0
ln -s /usr/lib64/libboost_iostreams.so.1.68.0 /usr/lib64/libboost_iostreams.so.1.67.0
ln -s /usr/lib64/libboost_filesystem.so.1.68.0 /usr/lib64/libboost_filesystem.so.1.67.0

waiting for someone to recompile Libreoffice with the new version of Boost

Alien Bob · 08-15-2018, 03:55 AM

I am in my third day of being unsuccessful at compiling the new LibreOffice 6.1.0 on -current so I will give in and compile a 6.0.6 version first, so that people have a working LibreOffice again.
Then I will keep on trying to compile 6.1.0.

orbea · 08-15-2018, 02:12 PM

Quote:

Originally Posted by Alien Bob

I am in my third day of being unsuccessful at compiling the new LibreOffice 6.1.0 on -current so I will give in and compile a 6.0.6 version first, so that people have a working LibreOffice again.
Then I will keep on trying to compile 6.1.0.

What's the issue? My own script still builds 6.1.0.3 fine after updating current.

Alien Bob · 08-15-2018, 02:28 PM

Quote:

Originally Posted by orbea

What's the issue? My own script still builds 6.1.0.3 fine after updating current.

When configuring "--with-system-boost" the build will trip over the missing /usr/include/boost/uuid/sha1.hpp in the /boost-1.68.0-x86_64-1.txz package of Slackware-current.
If I configure "--without-system-boost" then the linker fails to find the boost-system libraries that it compiled earlier, when linking liborcus.so.
Iterating a libreoffice build is tedious because of the long compile times. I can only look at it during evenings and I have been busy with a new Plasma Desktop also. So, I am a bit stretched thin and my patience is running out.
I looked at this: https://notabug.org/orbea/SlackBuild...ice.SlackBuild but that is for 6.0.6 which by the way is the same version I am trying to compile at the moment.

orbea · 08-15-2018, 02:46 PM

I ran into that too, its a libcmis bug. I have a fix for libcmis at SBo.

Code:

# Fix for boost-1.68.0 in current
[ -f /usr/include/boost/uuid/detail/sha1.hpp ] &&
  sed -i 's|boost/uuid/sha1.hpp|boost/uuid/detail/sha1.hpp|' \
  ./src/libcmis/xml-utils.cxx

However the internal version of libcmis is still broken.

I do my work in the staging branch and then merge to master around when SBo does the same.
https://notabug.org/orbea/SlackBuild...ce/libreoffice

Note that this link may not work in the future.

Edit: I also had no problem with the scripts for libixion and liborcus at SBo.

And here is a bug report for libcmis upstream.
https://github.com/tdf/libcmis/issues/19

Alien Bob · 08-15-2018, 02:57 PM

Thanks for your informative reply and the SlackBuild script. I am leaning toward abandoning mine and just using yours to compile a package now ...

cwizardone · 08-16-2018, 06:18 AM

Quote:

Originally Posted by Darth Vader

http://slackmirror.cbpf.br/pub/slack...are64-current/

The magic mirror which keep all packages since Ice Age. I needed it too some time ago, for an older linux-firmware.

@Darth,
Many Thanks!
Good to know!

orbea · 08-16-2018, 09:03 AM

Quote:

Originally Posted by Alien Bob

Thanks for your informative reply and the SlackBuild script. I am leaning toward abandoning mine and just using yours to compile a package now ...

Thanks, but I should warn you that my script is more than my computing resources can handle and my testing is minimal at times. Mostly I have not tried it on 14.2 in a while and I imagine some of the system library checks would fail there which would result in unintentionally using internal libraries. This should be relatively easy to check by checking the output of the accompanying swlodc.sh script. Additionally when updating it I try to build it successfully 3 ways, my own personal custom build, a default build and one with SYSTEM_LIBS=no to force internal libraries. However your issues with a mixture of the system boost and internal libraries makes me think I could maybe find more points of failure if I added a SBO_LIBS=no.

Also some of the configuration options like languages or java have very little testing...

Alien Bob · 08-16-2018, 09:40 AM

Quote:

Originally Posted by orbea

I ran into that too, its a libcmis bug. I have a fix for libcmis at SBo.

Code:

# Fix for boost-1.68.0 in current
[ -f /usr/include/boost/uuid/detail/sha1.hpp ] &&
  sed -i 's|boost/uuid/sha1.hpp|boost/uuid/detail/sha1.hpp|' \
  ./src/libcmis/xml-utils.cxx

However the internal version of libcmis is still broken.

I do my work in the staging branch and then merge to master around when SBo does the same.
https://notabug.org/orbea/SlackBuild...ce/libreoffice

Note that this link may not work in the future.

Edit: I also had no problem with the scripts for libixion and liborcus at SBo.

And here is a bug report for libcmis upstream.
https://github.com/tdf/libcmis/issues/19

I patched the internal libcmis with a similar solution as yours and now the compile/link against the system boost works. Let's see where the build ends... either with a 6.1.0 package or with some other (hopefully less cumbersome) error.

andrew.46 · 08-16-2018, 09:28 PM

Quote:

Originally Posted by chrisVV

Not to answer your question, but to run LibreOffice on slackware-current I have started using the app-image version available at https://www.libreoffice.org/download/appimage/ . That supplies its own version of boost and numerous other libraries. You need to make the file executable with chmod +x when you have downloaded it.

Now that does look interesting, is there any particular performance hit on your system running libreoffice this way?

montagdude · 08-16-2018, 10:30 PM

Quote:

Originally Posted by andrew.46

Now that does look interesting, is there any particular performance hit on your system running libreoffice this way?

I can't speak to whether there is any performance hit, but this interested me too. I am pretty impressed that I don't need any sort of appimage translator or library on my system to run it. I may think about deploying some of my own stuff this way in the future.