On 24.02.2016 14:52, Pranav Ganorkar wrote:
Hi,
I want to ask if anybody has been successful in building Libreoffice
recently on Archlinux. Do we need to use the switches given in PKGBUILD
<https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/libreoffice-fresh>
for
successful build ?
Regards,
Pranav
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Hi Pranav,
I've built LibreOffice recently on Archlinux, but didn't use PKGBUILD switches yet.
I had problems with building LO on Archlinux around the end of January, I guess, and it turned out
that there were two conflicts:
- extra/nvidia package - NVIDA drivers; I've set up bumblebee for NVIDIA Optimus and after that I
wasn't able to build LO again (it crashed on tests with OpenCL, IIRC),
- problem with new packages, I didn't have time to examine it, maybe it was a bug in one of them
or some changes in libraries (package replacement?); I downgraded system to the version from the
12th of December 2015 and I built LO without errors.
I've also built successfully LO three days ago (without updating system before), so from LO side
everything is OK. If you don't have bumblebee and still have problems, it seems that using switches
from that PKGBUILD is the only solution for fresh Archlinux after the New Year. I suppose that only
one switch (maybe three at most) is necessary. Let me now which one, if you find out ;-).
Regards,
Łukasz
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.