config/companion_libs/mpfr.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon May 25 17:26:21 2009 +0000 (2009-05-25)
branchgcc-4.4
changeset 1383 46658e3fc781
parent 1318 5416f4ba36bf
child 1386 7995942261f2
permissions -rw-r--r--
/devel/gcc-4.4:
- GMP: unconditionnaly build the C++ wrappers and use exceptions

-------- diffstat follows --------
/devel/gcc-4.4/scripts/build/companion_libs/gmp.sh | 11 2 9 0 ++---------
1 file changed, 2 insertions(+), 9 deletions(-)
     1 # GMP options
     2 
     3 choice
     4     bool
     5     prompt "MPFR version"
     6 
     7 config MPFR_V_2_3_1
     8     bool
     9     prompt "2.3.1"
    10 
    11 config MPFR_V_2_3_2
    12     bool
    13     prompt "2.3.2"
    14 
    15 config MPFR_V_2_4_0
    16     bool
    17     prompt "2.4.0"
    18 
    19 config MPFR_V_2_4_1
    20     bool
    21     prompt "2.4.1"
    22 
    23 # CT_INSERT_VERSION_ABOVE
    24 # Don't remove above line!
    25 endchoice
    26 
    27 config MPFR_VERSION
    28     string
    29     default "2.3.1" if MPFR_V_2_3_1
    30     default "2.3.2" if MPFR_V_2_3_2
    31     default "2.4.0" if MPFR_V_2_4_0
    32     default "2.4.1" if MPFR_V_2_4_1
    33 # CT_INSERT_VERSION_STRING_ABOVE
    34 # Don't remove above line!
    35 
    36 config MPFR_CHECK
    37     bool
    38     prompt "Check MPFR (!!! README !!!)"
    39     default n
    40     help
    41       It is highly recommended to check the newly built MPFR library.
    42       Unfortunately, this is a very intensive task, and takes a loooong time.
    43 
    44       Checking MPFR is thus disabled by default.
    45 
    46       If you suspect that your MPFR library is the cause for incorrectly
    47       generated code, you should answer 'Y' here.
    48