scripts: add support for building manuals

Add support for building the HTML and PDF manuals for the major
components. Implement for binutils, GCC, GDB, and GLIBC.

Always build all manuals and install a subset. Be explicit about the
subset to reduce the clutter and to avoid getting copies of common
manuals like bfd from all of the sourceware based components. Downside of
being explicit is that you need to update it when a new component
comes along.

Build the manuals as part of the last GCC build, namely 'cc' for glibc
based ones and cc_core_pass_2 for baremetal.

An example of the output is at:
http://people.linaro.org/~michaelh/incoming/crosstool-NG/

Signed-off-by: Michael Hope <michael.hope@linaro.org>
[yann.morin.1998@anciens.enib.fr: depends on ! remove docs; gold manual install]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

 #!@@CT_bash@@

 # What we need:

 #  - the .config file

 # Parse the tools' paths configuration

 . "${CT_LIB_DIR}/paths.mk"

 # We'll need the stdout later, save it

 exec 7>&1

 # Parse the common functions

 . "${CT_LIB_DIR}/scripts/functions"

 # Don't care about any log file

 exec >/dev/null

 rm -f "${tmp_log_file}"

 # Parse the configuration file

 . .config.2

 # Parse architecture and kernel specific functions

 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"

 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"

 # Build CT_TARGET

 CT_DoBuildTargetTuple

 # All this for this single echo... :-( Sigh, I'll have to re-arrange things...

 echo "${CT_TARGET}" >&7