[90899] trunk/dports/multimedia/ffmpeg-devel

[Jeremy Huddleston]

>> +# This is fixed in llvm-gcc trunk, but not in Apple's shipped llvm-gccs.
>> if {${configure.compiler} == "llvm-gcc-4.2"} {
>> -    configure.compiler gcc-4.2
>> -} elseif {${configure.compiler} == "clang"} {
>> -    depends_build-append port:apple-gcc42
>> -    configure.compiler apple-gcc-4.2
>> -    # base (as of 2.0.3) doesn't set cxx for apple-gcc-4.2
>> -    configure.cxx ${prefix}/bin/g++-apple-4.2
>> +    configure.compiler clang
>> }
> 
> This forces clang when llvm-gcc-4.2 is set but the latter is still a
> valid compiler on certain configurations of OSX/Xcode, isn't it?
> Is possibly #33735 [1] related to this clang forcing?

Yeah, but llvm-gcc-4.2 produces errors where even older clang doesn't.  See the output from my ffmpeg fate tinderbox using XCode 3.3's compilers as well as MP clang-3.0 and clang-3.1:
http://fate.ffmpeg.org/?asort=os

I'm looking into #33735 now.