Date: Mon, 03 Apr 2017 13:53:25 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 218330] [exp-run] Use the lang/gccX port(s) instead of lang/gcc for USE_GCC=yes Message-ID: <bug-218330-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218330 Bug ID: 218330 Summary: [exp-run] Use the lang/gccX port(s) instead of lang/gcc for USE_GCC=3Dyes Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Ports Framework Assignee: portmgr@FreeBSD.org Reporter: gerald@FreeBSD.org CC: freebsd-ports-bugs@FreeBSD.org, jbeich@FreeBSD.org Flags: exp-run? Created attachment 181428 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D181428&action= =3Dedit Proposed patch As of today, USE_GCC=3Dyes (and USE_GCC=3Dany in most circumstances) and consequently many of the USES=3Dcompiler settings use the canonical GCC port lang/gcc. With the new setup where I have introduced lang/gcc5-devel for weekly snapshots and lang/gcc5 for releases, and similarly for GCC 6 and onward, we can easily leverage lang/gcc5 (and later ports) for that role and indeed of today lang/gcc and lang/gcc5 are nearly identical (short of symlinks for gcc, g++, and gfortran binariesthe former provides). Once this patch has been tested successfully and committed, the next step will be stripping down lang/gcc to serve a similar function as lang/python. But, one step at a time. ;-) --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218330-13>