GMP and MPFR are no longer a sub-component of gcc (config-wise).
Build and install GMP and MPFR for the target.
Use the target GMP and MPFR to build the native gdb.
Have separate extra_config for cross gdb, native gdb and gdbserver.
Check native GMP and MPFR in //.

/trunk/scripts/build/debug/300-gdb.sh | 27 19 8 0 ++++++++++++++++-------
/trunk/scripts/build/gmp.sh | 47 39 8 0 ++++++++++++++++++++++++++++++++-------
/trunk/scripts/build/mpfr.sh | 49 40 9 0 +++++++++++++++++++++++++++++++++--------
/trunk/steps.mk | 2 2 0 0 ++
/trunk/config/cc/gcc.in | 18 1 17 0 +--------------
/trunk/config/debug/gdb.in | 6 1 5 0 +----
/trunk/config/config.in | 1 1 0 0 +
/trunk/config/gmp_mpfr.in | 34 34 0 0 ++++++++++++++++++++++++++++
8 files changed, 137 insertions(+), 47 deletions(-)

# GMP and MPFR libraries config options

menu "GMP and MPFR"

config GMP_MPFR

    bool

    prompt "GMP and MPFR"

    help

      Recent gcc needs both GMP and MPFR to build some frontends.

      Say 'Y' here if you want to build those two libraries specifically

      for crosstool-NG.

      The packages that can use GMP and MPFR are:

        - binutils

        - gcc

        - gdb

config GMP_MPFR_TARGET

    bool

    prompt "Build libraries for the target"

    depends on GMP_MPFR

    default n

    help

      Also build libraries for the target. This can be usefull if you want

      to later build a compiler that will run on the target, or if you want

      to run gdb natively on the target.

if GMP_MPFR

source config/cc/gmp.in

source config/cc/mpfr.in

endif

endmenu