https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61407
--- Comment #49 from Jeremy Huddleston Sequoia <jeremyhu at macports dot org> --- (In reply to Francois-Xavier Coudert from comment #45) > (In reply to Jeremy Huddleston Sequoia from comment #42) > > The committed patch is incorrect. It makes an invalid assumption which > > breaks the usage of deployment targets such as 10.9.3. > > All Apple doc I can find has deployment targets of the form 10.x or 10.x.0 > (where x is integer, but not only one digit). That is not the case. Do not make that assumption. (In reply to howarth from comment #46) > (In reply to Francois-Xavier Coudert from comment #45) > > (In reply to Jeremy Huddleston Sequoia from comment #42) > > > The committed patch is incorrect. It makes an invalid assumption which > > > breaks the usage of deployment targets such as 10.9.3. > > > > All Apple doc I can find has deployment targets of the form 10.x or 10.x.0 > > (where x is integer, but not only one digit). > > If Jeremy really disagreed on that change, he hasn't acted on it in the > gcc49 MacPorts packaging that he maintains (which still uses the original > proposed patch from > https://gcc.gnu.org/ml/gcc-patches/2014-08/msg02428.html). FYI, as far as > llvm-gcc 4.2.1 is concerned, in my fink legacy package for Apple's llvm-gcc > 4.2.1, I used a back port of our patch, > http://fink.cvs.sourceforge.net/viewvc/fink/dists/10.7/stable/main/finkinfo/ > languages/llvm-gcc42-yosemite.patch. Neither gcc 4.9.2 nor the patched > llvm-gcc 4.2.1 has shown any problems on OS X 10.9.5. I have not fixed the GPL3 ports in MacPorts because I do not read GPL-3 code and thus am not able to fix it. Another MacPorts developer is making the fix for newer versions of gcc.