[MacPorts] #38732: gcc48 is broken by configure-timespec.patch

[MacPorts]

#38732: gcc48 is broken by configure-timespec.patch
------------------------+--------------------
  Reporter:  howarth@…  |      Owner:  mww@…
      Type:  defect     |     Status:  closed
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.1.3
Resolution:  fixed      |   Keywords:
      Port:  gcc48      |
------------------------+--------------------

Comment (by howarth@…):

 Replying to [comment:28 jeremyhu@…]:
 > > So while the wrong unwinder is used
 >
 > Are you sure about that?  As I showed above, libstdc++.dylib is
 resolving its Unwind* symbols to libSystem...
 >
 > > , the code doesn't break because only a single unwinder is used.[[BR]]
 [[BR]]
 Try 'g++-mp-4.8 -std=c++11 test.cc' with the current gcc48 packaging and
 you will find the test case still segfaults.[[BR]]
 If this problem occurs only for darwin10 and later, we probably are
 running into the complexities with using static libs under the
 faster[[BR]]
 c++ weak-symbol coalescing introduced in darwin10. We have a similar
 problem in static linkage into libitm in FSF gcc[[BR]]
 (see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55693#c40 and
 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55693#c41 for[[BR]]
 details. Basically, when c++ weak-symbol coalescing was made faster, the
 cost was that non-weak symbols in libstdc++ dylib would now[[BR]]
 be overridden by those from a static lib linked in. It took us a long time
 to understand the subtly of that problem but the darwin[[BR]]
 linker developer helped us tease that issue out.

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