On Jan 17, 2012, at 3:46 PM, Ryan Schmidt wrote:
>
> On Jan 17, 2012, at 17:43, Jeremy Huddleston wrote:
>
>> That looks good to me, but I would very much like to know what ports fall
>> into this category, so I can check if this is still the case with
>> top-of-tree clang and file a bug against the compiler if necessary.
>>
>> I know wine falls into this category, but most "normal" ports should be fine
>> with clang (or llvm-gcc if clang doesn't work for some reason, but again
>> please file compiler bugs or poke me to do so).
>>
>> Also, as clang gets fixed for these issues in future XCodes, we should
>> change that ${configure.compiler} == "clang" to ${configure.compiler} ==
>> "clang" && [vercmp $xcodeversion Fixed.Version] < 0
>>
>> --Jeremy
>
> It's just so tedious. I don't have time to file all these bug reports and
> keep track of what versions of clang work. I'm happy if we can commit a fix,
> any fix, that lets a port compile.
If you don't have time to report bugs, they won't get fixed. That's why I said
you should tell me about it if you don't want to file the bug report, so I can
do it for you.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
