/devel/gcc-4.4:
- add support for building the MPC library.

-------- diffstat follows --------
/devel/gcc-4.4/scripts/build/companion_libs/ppl.sh | 4 2 2 0 +-
/devel/gcc-4.4/scripts/build/companion_libs/mpc.sh | 57 57 0 0 ++++++++++++++++++++++++++++++++++
/devel/gcc-4.4/scripts/build/companion_libs/cloog.sh | 4 2 2 0 +-
/devel/gcc-4.4/scripts/crosstool-NG.sh.in | 3 3 0 0 ++
/devel/gcc-4.4/steps.mk | 1 1 0 0 +
/devel/gcc-4.4/config/companion_libs/mpc.in | 32 32 0 0 +++++++++++++++++++
/devel/gcc-4.4/config/companion_libs.in | 15 10 5 0 ++++++---
7 files changed, 107 insertions(+), 9 deletions(-)

# MPC options

choice

    bool

    prompt "MPC version"

config MPC_V_0_6

    bool

    prompt "0.6"

# CT_INSERT_VERSION_ABOVE

# Don't remove above line!

endchoice

config MPC_VERSION

    string

    default "0.6" if MPC_V_0_6

# CT_INSERT_VERSION_STRING_ABOVE

# Don't remove above line!

config MPC_CHECK

    bool

    prompt "Check MPC (!!! README !!!)"

    default n

    help

      It is highly recommended to check the newly built MPC library.

      Unfortunately, this is a very intensive task, and takes a loooong time.

      Checking MPC is thus disabled by default.

      If you suspect that your MPC library is the cause for incorrectly

      generated code, you should answer 'Y' here.