> > @@ -115,6 +115,13 @@
> > post-destroot {
> > file delete -force ${destroot}${prefix}/share/man/man7 \
> > ${destroot}${prefix}/share/info
> > +
> > + # http://trac.macports.org/ticket/35770
> > + eval delete [glob ${destroot}${prefix}/lib/${name}/libstdc++*]
> > +
> > + # This symlink is provided as a transition aide and will be removed
> > + # with a future revision of this port.
> > + ln -s /usr/lib/libstdc++.6/dylib
> > ${destroot}${prefix}/lib/${name}/libstdc++.6.dylib
> > }
>
> There's a typo here (and in the other ports): the link should be to
> libstdc++.6.dylib not libstdc++.6/dylib
>
Thanks. I fixed that in a revbump. Sorry for the noise.
> But, aside from that, doesn't this break existing binaries that are
> linked against libstdc++?
No. That's the point of the symlink. It will allow binaries linked against
the previous runtimes to find the host's runtime.
> The different builds of libstdc++ don't seem
> to be compatible?
That's outlined in the bug report. You can't reliably have multiple C++
runtimes in the same process.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
