Problem with gcc4.7 and call_once

[Jeremy Huddleston Sequoia]

On Aug 8, 2013, at 8:04, David Barto <DBarto at visionpro.com> wrote:

> Interesting result of the build of libstdcxx
> 
> gcc 4.8 rebuilt because I removed the /opt/local/lib/libstdc++.6.dylib.

...

> When complete however /opt/local/lib/gcc48 has a symbolic link to /opt/local/lib/libstdc++.6.dylib

Yes, that's how it's supposed to be.

> which is NOT the version just built.

Do you have evidence of this?  It should be the same since it's built from the same sources in the same method and then just installed at the other location.

> In fact since the file ' /opt/local/lib/libstdc++.6.dylib' doesn't exist, the port package started the build over again. This seems reasonable.
> 
> However since the file that gets built is not installed, this appears to be the problem related to the std::call_once issue.

I doubt it.

> Any help on getting the port to install the proper file?

It is installing the proper file as the libstdcxx subport.

Please file this bug with gnu.org and feel free to provide my analysis.  As it is GPL3, I won't be looking at their source to figure out what went wrong.  I did verify that it is still an issue with gcc-4.9's libstdcxx, and you've already mentioned it was an issue with gcc-4.7, so it's not a recent regression.

--Jeremy

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4145 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20130808/bbc29dc6/attachment.p7s>