Hi all,
Ryan has proposed moving to gcc6 as the standard default version of the GCC
compiler, which would be done in the compilers portgroup. It sounds like a
good idea to me. Does anyone see a problem with that with their ports that
use the compilers portgroup? (If so, the default can always be overridden
in individual Portfiles.)
David
---------- Forwarded message ----------
From: MacPorts <nore...@macports.org>
Date: Tue, Jun 28, 2016 at 10:43 AM
Subject: Re: [MacPorts] #51724: compilers-1.0: default to gcc6
To: ryandes...@macports.org, macports-tick...@lists.macosforge.org
Cc: s...@macports.org, dstru...@macports.org
#51724: compilers-1.0: default to gcc6
---------------------------+--------------------------------
Reporter: ryandesign@… | Owner: macports-tickets@…
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: |
---------------------------+--------------------------------
Comment (by mf2k@…):
I switched to gcc6 for my ports and everything appears to work. However, I
believe such a change should be brought up on the dev list to make sure
that no one sees a problem with this.
{{{
$ port installed | grep gcc
eigen3 @3.2.8_0+gcc6 (active)
fftw-3 @3.3.4_1+gcc6 (active)
gcc6 @6.1.0_0 (active)
gcc_select @0.1_8 (active)
gsl @2.1_0+gcc6 (active)
hdf5 @1.10.0_1+cxx+gcc6+hl (active)
libgcc @6.1.0_0 (active)
py27-numpy @1.11.1_0+gcc6 (active)
py35-h5py @2.6.0_0+gcc6 (active)
py35-numpy @1.11.1_0+gcc6 (active)
py35-scipy @0.17.1_0+gcc6 (active)
}}}
--
Ticket URL: <https://trac.macports.org/ticket/51724#comment:1>
MacPorts <https://www.macports.org/>
Ports system for OS X
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
