gcc49 vs gcc48

Chris Jones jonesc at hep.phy.cam.ac.uk
Fri Oct 30 00:29:49 PDT 2015

On 30/10/15 01:18, Brandon Allbery wrote:
> On Thu, Oct 29, 2015 at 9:15 PM, David Strubbe <dstrubbe at macports.org
> <mailto:dstrubbe at macports.org>> wrote:
>     The problem that was being mentioned here is that gcc48 doesn't
>     build. That should not imply that ports already built with gcc48
>     have any problem. So there is no need to recompile anything. Just
>     when building new ports use a different version not gcc48.
> But there are ports (and I believe one of them was at the start of this
> thread) that bake specific compilers into themselves, and therefore have
> compiler-specific variants.
> That said, the fix for this is to look for any +gcc48 on ports to be
> installed and replace it with +gcc49. (Ports that had +gcc48 as default
> variant *should* use a different compiler already; if not, file a bug.)

or better yet, use +gcc5, to use the most recent stable gcc release.

More information about the macports-users mailing list