Date: Fri, 14 Jun 2019 19:55:32 +0200 (CEST) From: Gerald Pfeifer <gerald@pfeifer.com> To: Cy Schubert <Cy.Schubert@cschubert.com>, Alexey Dokuchaev <danfe@freebsd.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r504198 - head/Mk Message-ID: <alpine.LSU.2.21.1906141932170.3441@anthias.pfeifer.com> In-Reply-To: <20190614165425.GA42674@FreeBSD.org> References: <201906141610.x5EGAdnN049103@repo.freebsd.org> <F69E23F2-E526-4B3F-95EB-1786222C2D61@cschubert.com> <20190614165425.GA42674@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 Jun 2019, Cy Schubert wrote: > Does anything still depend on gcc49, 5 or 6 anymore? Yes and no. lang/gcc49 was pruned end of April, but lang/gcc48, which is even older, is still in use by two ports, though at least one is being worked on. I actually have a script running twice a week which checks such dependencies. Here is its relevant output: 2 refer to GCC 4.8. sysutils/memtest86+/Makefile:USE_GCC= 4.8 sysutils/uefi-edk2-bhyve/Makefile:USE_GCC= 4.8 0 refer to GCC 5. 1 refer to GCC 6. print/pdftk/Makefile:USE_GCC= 6 On Fri, 14 Jun 2019, Alexey Dokuchaev wrote: > 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. You're welcome, Alexey. Though the problem is users (!= danfe) who sometimes use those older versions and then report all sorts of interesting challenges. Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LSU.2.21.1906141932170.3441>