GCC driver-driver [was: Re: standard way to require c++11?]

Ryan Schmidt ryandesign at macports.org
Wed Apr 22 11:41:40 PDT 2015

On Apr 22, 2015, at 1:23 PM, Mihai Moldovan wrote:
> You're right. The proper solution would be to add the old driver-driver back to FSF GCC and get it upstreamed, instead of relying even more on muniversal.
> Personally, I do not wish to do so, for multiple reasons.

Too bad Apple didn't contribute the code back to FSF. Or maybe they did and they didn't accept it for some reason? I don't know. But this is the kind of thing I hate about forking projects.

More information about the macports-dev mailing list