[MacPorts] #31171: building gcc46 on osx lion fails

[MacPorts]

#31171: building gcc46 on osx lion fails
------------------------------+---------------------------------------------
 Reporter:  okpail@…          |       Owner:  mww@…           
     Type:  defect            |      Status:  new             
 Priority:  Normal            |   Milestone:                  
Component:  ports             |     Version:                  
 Keywords:                    |        Port:  gcc46           
------------------------------+---------------------------------------------

Comment(by dports@…):

 It seems like the problem here may be caused by to the platform block that
 adds --enable-fully-dynamic-string to configure.args. gcc46 builds fine
 for me once I remove it.

 --enable-fully-dynamic-string was added in r67282 in response to #22234
 (and subsequently to other gcc versions). The thinking there was that
 Apple's libstdc++ was compiled with _GLIBCXX_FULLY_DYNAMIC_STRING, so
 would create incompatibilities if trying to link against that and
 something compiled without it.

 I think that reasoning might have been mistaken. At least, it seems to be
 for Lion, where I don't see any evidence of libstdc++ being compiled with
 fully dynamic strings. The test file in #22234 works fine for me when
 using gcc46 built without --enable-fully-dynamic-string. See also Matt
 Seegmiller's comment in response to http://newartisans.com/2009/10/a-c
 -gotcha-on-snow-leopard/ which suggests that it isn't used on Snow Leopard
 either.

 Maybe the original issue was actually related to the use of
 _GLIBCXX_DEBUG, which boost used to be compiled with (#22112) and which
 was a source of known issues with Xcode 3.2?

 In any case, it seems like we should remove the `platform darwin 11` block
 that sets --enable-fully-dynamic-string, and probably the `platform darwin
 10` one too.

-- 
Ticket URL: <https://trac.macports.org/ticket/31171#comment:35>
MacPorts <http://www.macports.org/>
Ports system for Mac OS