Re: is anybody able to build libreoffice on archlinux

I build with:
--enable-dbgutil
--without-java
--without-help
--without-myspell-dicts
--without-doxygen

@Khaled
Do you have the newest version of packages? Perhaps Pranav and I have a "special" package, which 
covers some default library. E.g. I wasn't able to build LibreOffice with Python from Anaconda.

On 24.02.2016 18:26, Pranav Ganorkar wrote:
> I will surely let you know the switches if I am able to build
> successfully. By the way, my Archlinux is updated to latest packages.
I suppose that it will be one of '--with-system-*'. You could try to downgrade your system. It only 
requires changing three lines in /etc/pacman.conf, you can find more info on Arch wiki: 
https://wiki.archlinux.org/index.php/Arch_Linux_Archive#How_to_restore_all_my_packages_at_a_specific_date
As I wrote before, "Server=https://archive.archlinux.org/repos/2015/12/12/$repo/os/$arch"; works for 
me.
> But I am building the source on NTFS drive. Can that be the cause of problems ?
I think not, but you can always try to build from ext* partition, if downgrading won't fix that.
> And after pulling from latest master , I am getting this error:
>
> ************************************************************************************
> [LNK] Library/libdeploymentmisclo.so
> [LNK] Library/libmigrationoo2lo.so
> [LNK] Library/libmigrationoo3lo.so
> /mnt/D-Drive/LibreOffice/libreoffice/workdir/CxxObject/desktop/source/migration/services/oo3extensionmigration.o:
> In function
> `migration::OO3ExtensionMigration::scanDescriptionXml(rtl::OUString
> const&)':
> oo3extensionmigration.cxx:(.text+0x1031): undefined reference to
> `utl::SearchParam::SearchParam(rtl::OUString const&,
> utl::SearchParam::SearchType, bool, bool, bool)'
> oo3extensionmigration.cxx:(.text+0x1151): undefined reference to
> `utl::SearchParam::SearchParam(rtl::OUString const&,
> utl::SearchParam::SearchType, bool, bool, bool)'
> collect2: error: ld returned 1 exit status
> /mnt/D-Drive/LibreOffice/libreoffice/desktop/Library_migrationoo3.mk:10:
> recipe for target
> '/mnt/D-Drive/LibreOffice/libreoffice/instdir/program/libmigrationoo3lo.so'
> failed
> make[1]: ***
> [/mnt/D-Drive/LibreOffice/libreoffice/instdir/program/libmigrationoo3lo.so]
> Error 1
> make[1]: *** Waiting for unfinished jobs....
> Makefile:246: recipe for target 'build' failed
> make: *** [build] Error 2
>
> ****************************************************************************
Sorry, but I'm not sure, if I got similar error then. I only remember that first problem I had were 
failing tests.
> On Wed, Feb 24, 2016 at 10:37 PM, Łukasz Hryniuk <lukasz.hryniuk@wp.pl
> <mailto:lukasz.hryniuk@wp.pl>> wrote:
>
>     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
>         <mailto: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