Build failure in 4.4 branch with --enable-ext-google-docs on Xubuntu 14.04 amd64: "undefined reference to symbol 'dlclose@@GLIBC_2.2.5'"

Miklos Vajna vmiklos at collabora.co.uk
Mon Jan 26 01:04:31 PST 2015


Hi David,

On Sun, Jan 25, 2015 at 04:27:12PM +0000, David Gerard <dgerard at gmail.com> wrote:
> I want to write a blog post saying how I did
> this - before I do so, will there be a problem putting it up with that
> secret (which is presumably the one in every TDF build)? Should I use
> another one? If so, how do I obtain another one?

Even if it's not hard to get the TDF secret from the binaries, it's not
fair to advertise them. The more widely it's known, the more probable
that someone will reuse it in some nasty application, then the
TDF-registered app ID will get shut down, making LibreOffice users sad.

See here on how to obtain your own ID:

https://developers.google.com/drive/web/about-auth

If you write a blog post about this topic, that's great, but I guess
best to not mention any ID explicitly, they are kind of a secret anyway.

Regards,

Miklos
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.freedesktop.org/archives/libreoffice/attachments/20150126/1b2816e7/attachment.sig>


More information about the LibreOffice mailing list