Re: [MacPorts] #38814: libstdcxx and binaries linked against it can have conflicting emutls (one copy in libstdc++.dylib and one copy in libgcc_s.dylib) (was: libstdcxx subport's linkage on libgcc_eh.a incorrectly causes the usage of two different unwinders)

15 Apr 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@…):

 Right, so the issue seems to be the emutls symbols which are being linked
 statically instead of from libgcc_s.dylib
 {{{
 $ nm  /opt/local/lib/gcc48/libgcc_ext.10.5.dylib  | grep -v ' U ' | awk
 '{print $3}' | sort -u > /tmp/gccext
 $ comm -12 /tmp/gccext /tmp/libstdcxx
 ___emutls_get_address
 ___emutls_register_common
 }}}

 which seems to have nothing to do with the host's libunwind.

-- 
Ticket URL: <https://trac.macports.org/ticket/38814#comment:8>
MacPorts <http://www.macports.org/>
Ports system for OS X