1) It is not safe to use the [ command in configure.in; m4 will eat
the [ and ] and they will expand to nothing. (Just look in the
configure script produced prior to this commit.) Use the test command
instead, as elsewhere in the file.

2) Quote the variable being tested for emptiness with test
-z. Otherwise, if it *is* empty, the -z will apply to (and eat) the
following word, "then", which is not what is intended, and which also
causes a syntax error.

Because those two conditions were not very obvious.

This required a whole bunch of chnages all over the place.

This commit also update the internal includes to latest mozilla ones
including the .c{,pp} file updates.

The ldap check is also simplified from 2 check into plain one.

Use compiler options to default to more modern ARM architecture, as
surely any actual device this code would be run on uses.

That's what the NativeActivity stuff wants.

For now the name of the produced shared library does not follow the
normal libfoo.so convention, but is the name of the corresponding
program on normal Unixes. To be fixed later. Or then, when
constructing an app .apk, just rename "foo" to
"libnative-foo.so".

We use the "native app glue" thing from the NDK to avoid having to
have an explicit Java wrapper. (There is one provided by the OS's
NativeActivity anyway; all Android apps are Java programs.)

For simplicity, we just #include android_native_app_glue.c in
sal/main.h. sal/main.h is included only from source files that
actually form the "main" programs for our programs anyway, I hope.

Presumably the only programs we actually want to build for Android in
this way are unit tests. Any real (or toy) LibreOffice-related Android
app would have a totally Android-specific user interface written in
Java, and just call LO libraries, I think.

Simplest for now to have a copy of them in our sources. Improve later.