• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Sending a build message less severe then #warning
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sending a build message less severe then #warning


  • Subject: Re: Sending a build message less severe then #warning
  • From: Michael Crawford <email@hidden>
  • Date: Tue, 26 May 2009 09:33:39 -0700

On Tue, May 26, 2009 at 8:26 AM, Sam Krishna <email@hidden> 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.

Mike
--
Michael David Crawford
mdcrawford at gmail dot com

   GoingWare's Bag of Programming Tricks
      http://www.goingware.com/tips/
 _______________________________________________
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

  • Follow-Ups:
    • Re: Sending a build message less severe then #warning
      • From: Gwynne Raskind <email@hidden>
References: 
 >Re: Sending a build message less severe then #warning (From: Alex Curylo <email@hidden>)
 >Re: Sending a build message less severe then #warning (From: Sam Krishna <email@hidden>)

  • Prev by Date: Re: "Refactor..." menu item is disabled (Fairly exhaustive list of when this happens)
  • Next by Date: Re: Sending a build message less severe then #warning
  • Previous by thread: Re: Sending a build message less severe then #warning
  • Next by thread: Re: Sending a build message less severe then #warning
  • Index(es):
    • Date
    • Thread