config/companion_libs/mpfr.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Mar 28 01:05:18 2011 +0200 (2011-03-28)
changeset 2362 0888065f8c4d
parent 1784 dfadefc288c1
child 2436 c3e0c65b7b93
permissions -rw-r--r--
cc/gcc: cleanup the _or_later logic

So far, we've had a version always select appropriate _or_later option,
which in turn would select all previous _or_later options.

Because the dependencies on companion libs were cumulative, that was
working OK. But the upcoming 4.6 will no longer depend on libelf, so
we can't keep the cumulative scheme we've been using so far.

Have each release family select the corresponding dependencies, instead
of relying on selecting previous _or_later.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     1 # GMP options
     2 
     3 choice
     4     bool
     5     prompt "MPFR version"
     6 # Don't remove next line
     7 # CT_INSERT_VERSION_BELOW
     8 
     9 config MPFR_V_3_0_0
    10     bool
    11     prompt "3.0.0"
    12 
    13 config MPFR_V_2_4_2
    14     bool
    15     prompt "2.4.2"
    16 
    17 config MPFR_V_2_4_1
    18     bool
    19     prompt "2.4.1"
    20 
    21 config MPFR_V_2_4_0
    22     bool
    23     prompt "2.4.0"
    24 
    25 config MPFR_V_2_3_2
    26     bool
    27     prompt "2.3.2 (OBSOLETE)"
    28     depends on OBSOLETE
    29 
    30 config MPFR_V_2_3_1
    31     bool
    32     prompt "2.3.1 (OBSOLETE)"
    33     depends on OBSOLETE
    34 
    35 endchoice
    36 
    37 config MPFR_VERSION
    38     string
    39 # Don't remove next line
    40 # CT_INSERT_VERSION_STRING_BELOW
    41     default "3.0.0" if MPFR_V_3_0_0
    42     default "2.4.2" if MPFR_V_2_4_2
    43     default "2.4.1" if MPFR_V_2_4_1
    44     default "2.4.0" if MPFR_V_2_4_0
    45     default "2.3.2" if MPFR_V_2_3_2
    46     default "2.3.1" if MPFR_V_2_3_1