(Moving to macports-dev, which is long overdue. Prior history at
http://thread.gmane.org/gmane.os.apple.macports.user/35812)
On Sep 8, 2014, at 4:24 AM, Mojca Miklavec mo...@macports.org wrote:
On Sun, Sep 7, 2014 at 8:36 PM, Lawrence Velázquez wrote:
All this talk about keeping track of
On Sep 8, 2014, at 4:52 AM, Mojca Miklavec mo...@macports.org wrote:
It would be weird if we forced users to switch to a different runtime.
Herein lies the problem.
Users shouldn't be able to switch runtimes because there should not be more
than one runtime available. There should only be the
On Mon, Sep 8, 2014 at 1:24 PM, Lawrence Velázquez lar...@macports.org
wrote:
That's true, but it's a red herring. If our libstdc++ wasn't broken, ports
would not have to avoid it.
Our actual problem is that none of the g++ compilers we distribute are
viable because they don't use the
On Sep 8, 2014, at 2:08 PM, Brandon Allbery allber...@gmail.com wrote:
On Mon, Sep 8, 2014 at 1:24 PM, Lawrence Velázquez lar...@macports.org
wrote:
That's true, but it's a red herring. If our libstdc++ wasn't broken, ports
would not have to avoid it.
Our actual problem is that none of
On Mon, Sep 8, 2014 at 2:22 PM, Lawrence Velázquez lar...@macports.org
wrote:
- My first assertion is that MacPorts' libstdc++ is broken on OS X because
it doesn't use the system C++ runtime, libc++abi. This assertion, strictly
speaking, is not about C++11 support.
It strictly IS about C++11
On Mon, Sep 8, 2014 at 2:22 PM, Lawrence Velázquez lar...@macports.org
wrote:
- My first assertion is that MacPorts' libstdc++ is broken on OS X because
it doesn't use the system C++ runtime, libc++abi. This assertion, strictly
speaking, is not about C++11 support.
It strictly IS about
On Mon, Sep 8, 2014 at 2:35 PM, Lawrence Velázquez lar...@macports.org
wrote:
So if we start using our own libc++abi on older OS X, wouldn't C++
binaries built with Xcode's compilers be unable to interoperate with
binaries built with MacPorts compilers?
Only if you try to use it for
On Mon, Sep 8, 2014 at 2:44 PM, Brandon Allbery allber...@gmail.com wrote:
So the cases here are:
- pre-C++11 C++ support must use the system libstdc++ (the binary-only
backward compatibility one on newer systems whose development C++ runtime
is libc++).
- C++11 C++ support must either
