Date: Fri, 14 Jun 2019 17:58:22 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: Cy Schubert <Cy.Schubert@cschubert.com> Cc: Gerald Pfeifer <gerald@freebsd.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r504198 - head/Mk Message-ID: <20190614175822.GA3336@FreeBSD.org> In-Reply-To: <8BDC3B40-7FEA-46EA-AE7C-A3C266F6978F@cschubert.com> References: <201906141610.x5EGAdnN049103@repo.freebsd.org> <F69E23F2-E526-4B3F-95EB-1786222C2D61@cschubert.com> <20190614165425.GA42674@FreeBSD.org> <8BDC3B40-7FEA-46EA-AE7C-A3C266F6978F@cschubert.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 14, 2019 at 10:49:58AM -0700, Cy Schubert wrote: > On June 14, 2019 9:54:26 AM PDT, Alexey Dokuchaev <danfe@freebsd.org> wrote: > >On Fri, Jun 14, 2019 at 09:45:54AM -0700, Cy Schubert wrote: > >> ... > >> Does anything still depend on gcc49, 5 or 6 anymore? > > > >IDK, but I'm very grateful to Gerald for that he does not prune those > >actual ports from the tree. I'm still happily using GCC 4.8/5 as my > >default USE_GCC ports since they works just fine. > > A non-default gcc test doesn't duplicate what users are likely to use, > unless also testing using poudriere. These old GCC releases are often the only working solution for ports on sparc64/powerpc, so it still makes sense to keep them. Of course, I also keep local bsd.gcc.mk and bsd.default-versions.mk patches, but that's far easier than having to resurrect ports like I have to do for now-gone Qt 4 stack. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190614175822.GA3336>