Re: New compiler warning messages with Xcode 3.2.5 and gdb 4.2
Re: New compiler warning messages with Xcode 3.2.5 and gdb 4.2
- Subject: Re: New compiler warning messages with Xcode 3.2.5 and gdb 4.2
- From: David Reed <email@hidden>
- Date: Thu, 23 Dec 2010 10:37:23 -0500
On Dec 22, 2010, at 3:57 PM, Sean McBride wrote:
> On Wed, 22 Dec 2010 15:13:31 -0500, email@hidden said:
>
>>> After upgrading to the latest Xcode I'm getting a bunch of new
>> compiler warning messages
>>> (“The option ‘-D_GLIBCXX_DEBUG_PEDANTIC=1’ should not be passed to GCC
>> 4.2 and has been automatically suppressed.”) I've done a search of this
>> forum and the internet and it seems this message has been discussed.
>> However, the help offered in the old responses don't seem to apply in
> my case.
>>>
>>> Can anyone point me to some more recent help on this issue?
>>
>> There were issues with compiling C++ code with the gcc 4.2 versions that
>> came with Leopard and defining -GLIBCXX-DEBUG_PEDANTIC=1 allowed it to
>> compile correctly. With the versions of gcc 4.2 on Snow Leopard, that
>> bug was fixed and it's no longer necessary.
>>
>> You can either ignore the warning or go into your build settings and
>> remove that define (it's probably in your CFLAGS options.
>
> You sure about that? My understanding is that the STL debug mode is
> just totally broken on 10.6. And since Apple's doesn't much care about
> gcc anymore, it'll stay broken. clang does not have anything equivalent
> at this time anyway.
>
> --
> ____________________________________________________________
> Sean McBride, B. Eng email@hidden
> Rogue Research www.rogue-research.com
> Mac Software Developer Montréal, Québec, Canada
I'm not 100% certain (and sorry for not being). It was definitely broken on 10.5 - I don't think you could run any C++ code in DEBUG mode on 10.5 using gcc 4.2 if you didn't define that, but on 10.6 I didn't need to define that for what the little bit of C++ I was doing and it worked ok. I *think* that if you are not using the STL, you can ignore that error or remove the define. It appears if you are using the STL, there are still some issues in DEBUG mode - see below for a reply from Chris Espinosa (Apple employee) on Oct. 29, 2009:
Dave
<asked by someone else In Oct 2009>
> This brings up the question: is the debugging version of the standard C++
> library broken, or do we get debugging functionality automatically as a
> consequence of building a debug configuration?
>
> I just recently used these environment variables to track down a problem
> that I couldn't have found any other way...
<Chris Espinosa's reply on Oct 29, 2009>
Good news and bad news. Debugging of STL is not broken with gcc 4.2. But unfortunately, running apps in debug mode is due to FSF-driven changes in the ABI and not updating the libraries on SnowLeopard.
Your best bet is to build your Debug configurations with gcc 4.0 and your Release configurations with gcc 4.2.
_______________________________________________
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