Re: Sending a build message less severe then #warning
Re: Sending a build message less severe then #warning
- Subject: Re: Sending a build message less severe then #warning
- From: Sam Krishna <email@hidden>
- Date: Wed, 27 May 2009 06:32:37 -0400
<I suspect other Cocoa Jedi may smack me around for this next comment,
but here goes...>
Has anyone filed a RADAR for this? I don't want to sound pedantic, but
it does seem that if this is a *bug* or an *issue*, then wouldn't
filing a RADAR be appropriate? :-D
<...Sam says as he runs away from Gwynne's Force Lightning....>
Live Playfully,
Sam
-----
If he listens in faith,
finding no fault, a man is free
and will attain the cherished words
of those who act in virtue.
On May 26, 2009, at 1:23 PM, Gwynne Raskind wrote:
On May 26, 2009, at 12:33 PM, Michael Crawford wrote:
Couldn't I just build a new gcc codebase post-gcc-4.0.1 and use
that?
Wouldn't the patches already be in there?
You'd need to be sure to build Apple's version of GCC. While Apple
releases the source to its GCC, not all of its patches are merged
into
the upstream.
Which is a painful problem for those of us who want to use a
compiler that's not five years old... You simply *can't* use 4.3,
4.4, or 4.5 for OS X (or iPhone) development.
-- Gwynne, Daughter of the Code
"This whole world is an asylum for the incurable."
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden