You'll need to do that at the end of your build.

On Aug 8, 2013, at 14:51, David Barto <[email protected]> wrote:

> Start the install:
> 501_ sudo port install gcc48 +universal 
> .
> Snip
> .
> --->  Applying patches to libstdcxx
> --->  Configuring libstdcxx
> --->  Building libstdcxx
> ^C
> 502_ pushd 
> /opt/local/.../_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libstdcxx/work
> 
> 503_ find . -name 'config.log'
> ./build/build-x86_64-apple-darwin12/fixincludes/config.log
> ./build/build-x86_64-apple-darwin12/libiberty/config.log
> ./build/config.log
> ./build/fixincludes/config.log
> ./build/gcc/config.log
> ./build/intl/config.log
> ./build/libbacktrace/config.log
> ./build/libcpp/config.log
> ./build/libdecnumber/config.log
> ./build/libiberty/config.log
> 524_ find . -name 'config.log' | xargs egrep _GLIBCXX_HAS_GTHREADS
> 
> On Aug 8, 2013, at 2:08 PM, Jeremy Lavergne <[email protected]> 
> wrote:
> 
>> Look inside 'port work ...'
>> 
>> "Brian D. McGrew" <[email protected]> wrote:
>>> On 8/8/13 2:00 PM, "Jeremy Huddleston Sequoia" <[email protected]>
>>> wrote:
>>> 
>>> 
>>>> 
>>>> On Aug 8, 2013, at 13:53, Jeremy Huddleston Sequoia
>>>> <[email protected]> wrote:
>>>> 
>>>>> 
>>>>> On Aug 8, 2013, at 12:58, David Barto <[email protected]> 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
>>> [email protected]
>>> https://lists.macosforge.org/mailman/listinfo/macports-users
>> 
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users

Reply via email to