Problem with gcc4.7 and call_once

[Brian D. McGrew]

Port uninstall gcc48 --follow-dependents
Port uninstall libstdcxx --follow-dependents

Sudo port edit gcc48

Add --enable-libstdcxx-threads just below --enable-libstdcxx-time

Sudo port edit libstdcxx Š should be the same file as gcc48 (and your
change should be there).

Port install gcc48

And it doesn't the threading doesn't work - like it ignored the
--enable-libstdcxx-threads.

And in fact, the install was way way too fast for gcc-4.8.1 to be built
for sources (take a couple hours on my super linux box).

SoŠ  I'm wondering if there's a binary cache or something within ports
that I need to blow up to convince ports to rebuild libstdcxx and gcc49
from sources???




-brian
-- 


Brian McGrew
brian at visionpro.com




On 8/8/13 7:45 PM, "Jeremy Huddleston Sequoia" <jeremyhu at macports.org>
wrote:

>You'll need to do that at the end of your build.
>
>On Aug 8, 2013, at 14:51, David Barto <DBarto at visionpro.com> 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
>><jeremy at lavergne.gotdns.org> wrote:
>> 
>>> 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
>>> 
>> 
>