[MacPorts] #35770: gcc ports should not include a C++ runtime
MacPorts
noreply at macports.org
Tue Sep 11 16:18:01 PDT 2012
#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 jonesc@…):
Replying to [comment:29 alexander.afanasyev@…]:
> I also vote to return to the previous state, at least until there is a
separate libstc++ port.
>
> I agree that the instability from comment #2 is not theoretical and I
can easily reproduce it. At the same time, I can easily solve the problem
by stopping mixing the compilers when I compile my code. Long time ago
there was already a ticket for "pointer being freed was not allocated"
error, where the a suggested solution. While the solution is not really
working, the key point is not mixing stuff.
>
> Those who is not using gc4[4-8] have no problem. Those who are using,
just need to accept the fact that there is an incompatibility if compilers
are mixed. The removal of std++ solve solvable problem for a subset of
developers using gcc, but creates unsolvable problem for others who rely
on c++11 and other new features of standard library.
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.
--
Ticket URL: <https://trac.macports.org/ticket/35770#comment:31>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list