| 5 | 5 | The other doable workaround is to install '''the complete''' MacPorts with `libc++`. I tried it a few days ago and `mkvtoolnix` works. Jeremy also says that he has all of his machines running on `libc++` without any major issues. And that he's not willing to spend time patching things for `libstdc++`. I would actually like to suggest that MacPorts should '''really''' start supporting that setup officially. If it doesn't, it will pretty soon become useless on < 10.9. And that probably doesn't even mean unmanageable manpower. After Jeremy did the initial patching and after the release of 2.3.0 many things simply work out-of-the-box. And I would be willing to invest time into patching things. Some other people probably as well. The prerequisite though (chicken-and-egg problem) would be to set up two additional buildbots to provide binary packages. I'm willing to spend extra time providing patches, but I'm not wiling to compile the whole TeX Live, Qt, clang, root etc. after every single revbump. Last time I tried root compiled for 4 hours. But if we wait for too long, we'll miss the train. I that won't be done in the following few months, I will probably upgrade from 10.7 to 10.10 and I won't be willing to spend time patching the old stuff. And many other users will upgrade as well, sooner or later, so the pool of those willing to help will keep shrinking way below the critical mass. If we don't do that now, it will make less and less sense and macports users on < 10.9 will be more and more stuck with the old stuff. And before we realize we'll be bitten by C++14 and C++17 incompatibilities on 10.9 anyway ;). |
