* [build]: resolving OpenFst compilation issue with  gcc-6.x (#1392)

* [egs] Add new graphemic system for Gale Arabic, with newer nnet scripts (#1298)

* [build] Windows build: generate missing base/version.h; cosmetic changes (#1397)

* [build]: Enable cross compilation, including to android. (#726)

If a user has a number of tool chains installed and they do not want to
use the default, they must currently edit the kaldi.mk file after
running configure to change the CC, CXX, AR, AS, and RANLIB variables.
This is something that should be exposed via the configure script. This
patch exposes an option to set the host triple for the desired tool
chain in the configure script.

Building Kaldi on my Raspberry Pi boards is not particularly fast.  I
have been using the following patch to build kaldi executables for use
on the Pi boards for the better part of a year.  A typical invocation
for me is something like:

$ ./configure --static --atlas-root=/opt/cross/armv8hf \
--fst-root=/opt/cross/armv8hf --host=armv8-rpi3-linux-gnueabihf \
--fst-version=1.4.1

This way I can build on my much faster x86 desktop, but still run
experiments on ARM.

I have included support for cross compiling for ppc64le and it works for
me (at least it produces binaries for ppc64le I don't have a ppc64
machine to test it).

Signed-off-by: Eric B Munson <eric@cobaltspeech.com>

* Add mk file and configure options for building for Android

Building for Android requires a toolchain that can be built using the
Android NDK.  It works similiarly to the linux build except that it only
uses clang, only supports the openBLAS math library, and requires an
additional include directory for the system C++ headers.

A typical configure invocation looks like:

./configure --static --openblas-root=/opt/cross/arm-linux-androideabi \
--fst-root=/opt/cross/arm-linux-androideabi \
--host=arm-linux-androideabi --fst-version=1.4.1 \
--android-includes=/opt/cross/arm-linux-androideabi/sysroot/usr/include

Signed-off-by: Eric B Munson <eric@cobaltspeech.com>

* Make pthread cancel symbols noops for Android

The Android C library does not support cancelling pthreads so the
symbols PTHREAD_CANCEL_STATE and pthread_setcancelstate are undefined.
Because a pthread cannot be cancelled in Android, it is reasonable to
make the pthread_setcancelstate() call a noop.

Signed-off-by: Eric B Munson <eric@cobaltspeech.com>

* A few small fixes for configure

* Reword the clang++ requirement for android builds.

[egs,scripts]: add Swbd/s5c tuning scripts; simplify nnet3+chain 'combination' stage (doesn't affect results; faster); minor info-script fix.

[src,egs,scripts]: various minor fixes: make num-epochs continuous; add decay-time to other LSTM types; bug-fix in nnet3 combination code; swbd/s5c results added.

[src,egs,scripts]: improve use of sum-to-one penalty in combination, provide script support; examples of use of dropout in TDNN+LSTMs; change minibatch-size in combination phase.

Conflicts:
	egs/wsj/s5/steps/libs/nnet3/xconfig/lstm.py

Conflicts:
	src/nnet3/nnet-chain-combine.cc
	src/nnet3/nnet-combine.cc

The scripts used a hard-coded path including '_sp' suffix irrespective of whether speed_perturb is set.

Conflicts:
	egs/wsj/s5/steps/libs/nnet3/train/chain_objf/acoustic_model.py
	egs/wsj/s5/steps/libs/nnet3/train/frame_level_objf/common.py
	egs/wsj/s5/steps/nnet3/report/generate_plots.py
	egs/wsj/s5/steps/nnet3/train_dnn.py
	egs/wsj/s5/steps/nnet3/train_raw_dnn.py
	src/nnet3/nnet-combine.cc
	tools/extras/openfstwin-1.3.4.patch