Falling back on clang from llvm-gcc in gcc* ports (was: request for newer binutils (2.21))

[Jeremy Huddleston]

mww: Do you mind if I push a change as described below for gcc43 through gcc46?

On Jul 10, 2011, at 11:18 AM, Rainer Müller wrote:

>> I was pointed to this report
>>    https://trac.macports.org/ticket/29104
>> A pretty serious problem. One cannot compile gcc or migw gcc or
>> anything else at all.
>> 
>> I would love to submit the problem to Apple, but as someone else
>> pointed out: it is more productive to write to /dev/null than losing
>> time filing bug reports to Apple. I've been waiting for them to
>> resolve at least three serious bugs forever.
> 
> Actually this is a bug in llvm-gcc:
> 
>  http://llvm.org/bugs/show_bug.cgi?id=9571
> 
> I guess Apple just wouldn't care about bootstrapping gcc. But we could
> use clang instead to bootstrap gcc on systems with Xcode 4.0 or newer.

Yeah, the gcc* ports that I recently patched all build fine with clang.  I actually didn't even try using llvm-gcc before I made the clang/darwin11 fixes.  I'd suggest just using clang instead if the default compiler is llvm-gcc.

--Jeremy