Problem with gcc4.7 and call_once

[Jeremy Lavergne]

Look inside 'port work ...'

"Brian D. McGrew" <brian at visionpro.com> wrote:
>On 8/8/13 2:00 PM, "Jeremy Huddleston Sequoia" <jeremyhu at macports.org>
>wrote:
>
>
>>
>>On Aug 8, 2013, at 13:53, Jeremy Huddleston Sequoia
>><jeremyhu at macports.org> wrote:
>>
>>> 
>>> On Aug 8, 2013, at 12:58, David Barto <DBarto at visionpro.com> wrote:
>>> 
>>>> It appears that the following is missing from the configuration for
>>>>libstdc++.
>>>> 
>>>> --enable-libstdcxx-threads
>>>> Enable C++11 threads support. If not explicitly specified, the
>>>>configure process enables it if possible. It defaults to 'off' on
>>>>Solaris 9, where it would break symbol versioning. This option can
>>>>change the library ABI.
>>>> 
>>>> Yes, it changes the ABI, however for std::call_once to work, I
>think
>>>>it is required. I don't think that the configuration process is
>setting
>>>>it by default.
>>> 
>>> What makes you say that?  It looks like it is to me:
>>
>>...
>>
>>> Is your _GLIBCXX_HAS_GTHREADS undefined for some reason?  That
>doesn't
>>>make sense...
>>
>>
>>Yeah, it looks fine to me:
>>
>>libstdc++-v3/config.log:#define _GLIBCXX_HAS_GTHREADS 1
>>
>
>Where is the config.log?  Over in
>/opt/local/var/macports/software/libstdc++ all I find is a tar ball of
>the
>library???
>
>
>
>_______________________________________________
>macports-users mailing list
>macports-users at lists.macosforge.org
>https://lists.macosforge.org/mailman/listinfo/macports-users