Nah. Sure, doing it like that is sane if you consider only our own
code. But it won't help in making sure these options are used when
compiling the 3rd-party external libraries. For that having the
options already in the CC and CXX environment variables works nicely,
I think. People just need to look at the samples in README.cross.

Perhaps we could add the options to CC and CXX in configure.in,
though? Is that elegant or not, don't know...

This reverts commit 3c4f7242.

The findrequires scripts are apparently ignored by current RPM.
Apparently an additional variable needs to be defined so they are used.

http://www.redhat.com/archives/rpm-list/2005-August/msg00034.html

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.