Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


(originally filed as Bug 87293, but I was redirected here)


I am attempting to build with the Google Drive connection:
./autogen.sh --enable-ext-google-docs --with-gdrive-client-secret ; make

This is happening consistently for me, building latest libreoffice-4-4
from git, if I use --enable-ext-google-docs at all:

...
[build DEP] LNK:Executable/outdevgrind
[build LNK] Executable/outdevgrind
[build DEP] LNK:Executable/vcldemo
[build LNK] Executable/vcldemo
/usr/bin/ld: /home/fun/libreoffice/workdir/LinkTarget/StaticLibrary/libglxtest.a(glxtest.o):
undefined reference to symbol 'dlclose@@GLIBC_2.2.5'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libdl.so:
error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make[1]: *** [/home/fun/libreoffice/workdir/LinkTarget/Executable/icontest]
Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [build] Error 2


The build completes successfully on master (although in that case,
Google Drive doesn't show up as a CMIS option). The above error
happens trying to build libreoffice-4-4 for the past few days.

If I build 4.4 with just ./autogen.sh ; make then it builds.

I'm running an up-to-date Xubuntu 14.04 amd64.

If you could assist, that would be most helpful :-)


(I really, really want an LO that will connect to GDrive
transparently. The Windows build of 4.3 or 4.4beta1 connect and works
fine on Windows 7, but fail in Linux under Wine, for which I've filed
https://bugs.winehq.org/show_bug.cgi?id=37674 .)


- d.

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.