[MacPorts] #38814: libstdcxx and binaries linked against it can have conflicting emutls (one copy in libstdc++.dylib and one copy in libgcc_s.dylib)
MacPorts
noreply at macports.org
Mon Apr 15 13:40:54 PDT 2013
#38814: libstdcxx and binaries linked against it can have conflicting emutls (one
copy in libstdc++.dylib and one copy in libgcc_s.dylib)
------------------------+------------------------
Reporter: howarth@… | Owner: jeremyhu@…
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.1.3
Resolution: | Keywords:
Port: libstdcxx |
------------------------+------------------------
Comment (by jeremyhu@…):
Replying to [comment:10 howarth@…]:
> Placing the libgcc*dylib in a separate subport seems rather excessive
considering. To properly FSF gcc, full bootstraps should be used and you
are now tripling the number of bootstraps required to install gcc48.
As you've mentioned already:
* The failure to bootstrap was not the issue.
* Many users are getting these as binary packages and thus the
bootstrapping issue is not such a concern for them if we decided to go
that route.
If we do want to put these both into one port, I'd prefer calling the
ports something like gcc-runtime and gcc-runtime-devel (and obsoleting the
libstdcxx ports for them).
--
Ticket URL: <https://trac.macports.org/ticket/38814#comment:11>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list