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>

This is a somewhat ordered TODO list:

Recurring tasks:

- update versions for every tools...

- update and/or upgrade all samples

Non-recurring tasks:

- update newlib (for enhanced bare metal)

  - confirm existing implementation on targets other than AVR32

  - try to make it generic, will help for uClibc++

- multilib

- Cygwin target (needs newlib)

  - so we can build toolchains that generate code for Windows/Cygwin

- Cygwin host

  - so we can build toolchains that run natively under Windows/Cygwin

- mingw32 target

  - so we can build toolchains that generate code for Windows/Win32

- mingw32 host

  - so we can build toolchains that run natively under Windows/Win32

    (without requiring Cygwin)

- uClibc++

  - see newlib, above

- uClinux

  - check whether we can use newlib under uClinux (?)