Libreoffice-5.1.0.3
I've updated my libreoffice slackbuild to 5.1.0.3 and it seems to be working well so far, so here it is in case anyone is interested and willing to spend the time compiling it. I've also updated some of the optional dependencies, so grab them from my NAB repo if needed. The slackbuilds on SBo might be out of date given how I can't submit new slackbuilds yet. Make sure to read the README below before compiling to customize the build to your liking, or just run the script to get a fairly default build.
https://notabug.org/orbea/Slackbuild...ce/libreoffice Code:
LibreOffice is a productivity suite that is compatible with other major |
Hello
I get the following libraries showing as not installed when running the swlodc.sh script on a fresh (full including kde/kdei) install of -current (8th Feb snapshot 32 bit DVD with updates applied this morning). Code:
root@illy:/home/keith/Downloads/lo# ./swlodc.sh | grep "not installed" Thanks for your efforts. |
No, you don't, you only need them before running the script if you want to build against system versions of the packages instead of static versions which libreoffice will download during the build process. Some of them can also be disabled or have to be enabled like graphite2 and libeot as described in the README.
That script is mostly to make it easier to maintain the slackbuild which will detect if those packages are installed and use --with-system-package if so, I included it with the slackbuild in case someone else finds it useful. Edit: Just to be clear, the only required dependency not included in Slackware already is perl-archive-zip which a slackbuild for can be found at SBo. https://slackbuilds.org/repository/1...rl-archive-zip |
Hello
Thanks for reply, perfectly clear now, and I installed the perl module from the slackbuild you mentioned. An attempt at compilation using the command line below Code:
# TMP="/home/keith/tmp" OPT="yes" NUMJOBS="2" ./libreoffice.SlackBuild Code:
Makefile:244: recipe for target 'build' failed Code:
/home/keith/tmp/libreoffice-5.1.0.3/pyuno/source/module/pyuno.cxx:387:1: error: 'Py_hash_t' does not name a type Any suggestions gratefully received. This is a test machine only nothing critical. Cheers |
The numjobs are set to 1 for a reason, its a really heavy build and even with my amd 6-core cpu its best just to use 1 job even if its much slower...
Though I'm not sure that is the issue and I haven't run into anything similar either, but then I haven't tested this in a 32-bit environment. I can see if I can reproduce your problem tonight, but if its a problem with libreoffice itself rather than my script its probably best to ask in #libreoffice-dev @ freenode or on their mailing list. Are you trying this with slackware 14.1 or current? Also, do you have python3 installed? (Edit: nvm you don't according to your swlodc.sh paste. :)) |
Hello Orbea
Thanks for reply, and this is on -current 32bit full install updated to 13th Feb and it does not have python3 installed. I'll try running it without setting the numbjobs option which will result in a single thread after installing python3 and see where it gets to & then try the LO people Thanks for time & testing on 32 |
I like my libreoffice to be stable so I only use the Still stream described as
Quote:
Quote:
My business depends on having a stable version of Libreoffice Base so I'm waiting for the Still version 5.1 to appear before upgrading from 4.4.7. There was a serious bug introduced in version 5.0 that causes by whole machine to lock up. It's fixed in version 5.1. I'm conservative, so waiting for the good people at Libreoffice to say that Version 5.1 is ready for production use in a conservative environment. Alex |
Quote:
This little project is for lutz and giggles and to test out actually compiling something huge like LO. If the build fails again, I shall try a fresh install of a 64bit -current and see if that builds OK as orbea's has done. Then I can try and learn enough to find out what the problem is with a 32 bit compile. Cheers all |
Libreoffice fresh as compiled by my slackbuild is very stable for me, but it seems I was able to reproduce keithpeter's issue in a clean Slackware32-current chroot with one numbjob.
My current working hypothesis is that there is either a problem with compiling against python2 in the new libreoffice (Wasn't present in previous versions) or that there is a problem building it in a 32-bit environment. Some possible ways you might be able to work around this is by installing python3 which libreoffice compiles fine against in Slackware64-current, or by using one of these build options: PYTHON="no|internal|full". I'm not sure what features you would lose by disabling python... I'll see if I can get it to build again, but given that it takes me a good ~7 hours to build successfully with one job it will take a little bit. Code:
[CXX] pyuno/source/module/pyuno.cxx |
Hello Orbea
Yes, it was that Python related object that generated the error last time. I'm compiling with python3 installed on the 32bit -current installation used previously with the tmp directory cleared. The command line was Code:
#TMP="/home/keith/tmp" OPT="yes" ./libreoffice.SlackBuild Compilation completed in 7.5 hours or so and resulting package installed fine and working. It appears Python 3 is a requirement for building under 32 bit -current. RAM never much over 1Gb and laptop remained cool/luke warm throughout with some fan activity. Using the command line below Code:
#TMP="/home/keith/tmp" OPT="yes" DICT="yes" HELP="yes" NUMJOBS="2" ./libreoffice.SlackBuild |
Quote:
|
Quote:
http://www.slackware.com/~alien/slac...e50.SlackBuild http://www.slackware.com/~alien/slac...build/sources/ Cheers & thanks for the time you spent on tracking down the halfbuzz version issue in the thread at http://www.linuxquestions.org/questi...-a-4175572225/ |
Quote:
http://www.slackware.com/~alien/slac...ice.SlackBuild |
Quote:
|
I've tested this both on a 32 and 64-bit build environments, it seems the upstream libreoffice devs have since broken building libreoffice with python2 which was working in previous versions. I'm pretty sure I can work around this by forcing an internal version of python if python3 is not installed, I will update my slackbuild later assuming my changes work.
Quote:
|
All times are GMT -5. The time now is 02:38 AM. |