Blacklisting compiler versions or build numbers

[Ryan Schmidt]

On Nov 25, 2012, at 20:11, Jeremy Huddleston Sequoia <jeremyhu at macports.org> wrote:

> On Nov 25, 2012, at 3:10 PM, Craig Treleaven <ctreleaven at cogeco.ca> wrote:
> 
> For mythtv-core.25, I tested a bunch of compilers to find a few that worked.  Eg:
>> 
>> # See https://trac.macports.org/ticket/35934
>> compiler.blacklist  llvm-gcc-4.2 macports-llvm-gcc-4.2 macports-clang-3.1 \
>>                   dragonegg-3.0 dragonegg-3.1 apple-gcc-4.2
>> compiler.fallback-append macports-clang-3.0
>> 
>> # Run time failures with XCode 4.4.x and 4.5.0
>> if {[vercmp $xcodeversion 4.4] >= 0} {
>>   compiler.blacklist-append clang
>> }
>> 
>> # TODO: This should be done by base
>> # https://trac.macports.org/ticket/32542
>> if {${configure.compiler} == "macports-clang-3.0"} {
>>   depends_build-append port:clang-3.0
>>   depends_skip_archcheck-append clang-3.0
>> }
>> 
>> Assuming that some future version of Apple clang starts working (say the "444", above), how would this be expressed?
> 
> Using my example:
> compiler.blacklist-append {clang < 444}


No, according to the above, mythtv compiles fine with clang from Xcode older than 4.4. So it should be using the other example we had:

compiler.blacklist-append {clang >= YYY < 444}

Where "YYY" should be replaced with whatever build number corresponds to the first build number that fails to build mythtv (e.g. the build number of the clang included with Xcode 4.4's command line tools).