Proposal:
Since it seems that we are flat-out disallowing gcc being used as a
C/C++ compiler, I think it's time to do some clean up of the code:
1) Rename gccXY to gcc-X.Y
2) Rename +gccXY variants to +gfortranXY
3) Start moving away from configure.compiler=macports-gcc*
I think it's
On Oct 1, 2014, at 12:48 PM, Sean Farley wrote:
Proposal:
Since it seems that we are flat-out disallowing gcc being used as a
C/C++ compiler, I think it's time to do some clean up of the code:
1) Rename gccXY to gcc-X.Y
As I proposed earlier, we might want to avoid using a dash in a
Ryan Schmidt writes:
On Oct 1, 2014, at 12:48 PM, Sean Farley wrote:
Proposal:
Since it seems that we are flat-out disallowing gcc being used as a
C/C++ compiler, I think it's time to do some clean up of the code:
1) Rename gccXY to gcc-X.Y
As I proposed earlier, we might want to
On Oct 1, 2014, at 12:26 PM, Sean Farley s...@macports.org wrote:
Ryan Schmidt writes:
On Oct 1, 2014, at 12:48 PM, Sean Farley wrote:
Proposal:
Since it seems that we are flat-out disallowing gcc being used as a
C/C++ compiler, I think it's time to do some clean up of the code:
1)
On Oct 1, 2014, at 3:08 PM, Frank Schima m...@macports.org wrote:
On Oct 1, 2014, at 12:26 PM, Sean Farley s...@macports.org wrote:
We really should be consistent then. I personally don't care what the
new name is but we should either have clangX.Y / gccX.Y or clangXY /
gccXY.
I say we
Frank Schima writes:
On Oct 1, 2014, at 12:26 PM, Sean Farley s...@macports.org wrote:
Ryan Schmidt writes:
On Oct 1, 2014, at 12:48 PM, Sean Farley wrote:
Proposal:
Since it seems that we are flat-out disallowing gcc being used as a
C/C++ compiler, I think it's time to do some
