[MacPorts] #35770: gcc ports should not include a C++ runtime

[MacPorts]

#35770: gcc ports should not include a C++ runtime
--------------------------------------------------+------------------------
  Reporter:  jeremyhu@…                           |      Owner:  jeremyhu@…
      Type:  defect                               |     Status:  closed
  Priority:  Normal                               |  Milestone:
 Component:  ports                                |    Version:  2.1.2
Resolution:  fixed                                |   Keywords:  libstdc++
      Port:  gcc43 gcc44 gcc45 gcc46 gcc47 gcc48  |
--------------------------------------------------+------------------------

Comment (by jeremyhu@…):

 Replying to [comment:30 jonesc@…]:
 > Thanks but can I also request that the changes are reverted until this
 is done, if it is going to take a bit of time. The current situation with
 totally broken compilers, that users cannot use to build the simplest
 standalone code, is really not ideal...

 Reverting the changes is a waste of time, IMO.  I don't want to force
 users to rebuild again and then change it back and have them rebuild yet
 again.  I'm already working on the libstdc++ port based on libc++sup.
 That's a fairly straightforward thing to implement.  The *real* fix is
 going to be moving this to libc++abi, but until that is done, this
 libstdc++ will be no more broken than the old way.

 After it's in place, I'll bump the gcc ports again to have them depend on
 it and setup their symlink to point to it instead of /usr/lib/libstdc++.

 Replying to [comment:31 jonesc@…]:
 > Exactly my point. Please remember that the gcc4X compilers are *not*
 just there to provide alternative options to build ports, but people also
 use them to build their own code. If I install the latest gcc4X, it might
 well be because I really do want the new features that come with that new
 compiler.

 Unfortunately the gcc4X ports are not useful for actually shipping code to
 end users.  They're simply hobbyist compilers as they are now.  I'm trying
 to help get them to a more usable state.

 Replying to [comment:32 angelo.graziosi@…]:
 > At this point it is obvious that the changes in GCCs are totally
 wrong... I have seen anywhere that an "hybrid" (GCC47 and friends +
 libstd++ from GCC42) will work.
 >
 > So, the minimum, is reverting the changes until the ideas become more
 clear...

 What ideas do you want to "become more clear" ... ?

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