Date: Sat, 15 Jun 2019 13:43:32 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: Mark Linimon <linimon@lonesome.com> Cc: Cy Schubert <Cy.Schubert@cschubert.com>, 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: <20190615134332.GA32655@FreeBSD.org> In-Reply-To: <20190615061345.GA20346@lonesome.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> <20190614175822.GA3336@FreeBSD.org> <20190615061345.GA20346@lonesome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 15, 2019 at 06:13:46AM +0000, Mark Linimon wrote: > On Fri, Jun 14, 2019 at 05:58:22PM +0000, Alexey Dokuchaev wrote: > > These old GCC releases are often the only working solution for ports > > on sparc64/powerpc > > I'm not aware of the powerpc dependencies. Do you have a list? > We are actively working on ports on powerpc (especially powerpc64). Actually, things look better on powerpc, last time I recall I was able to successfully build gcc7 port for it. Typically I'd use earlier versions because they take less tmpfs space and faster to build. > w/rt sparc64, I no longer consider sparc64 viable. There is too much > pushback whenever I mention it. My development machines were powered > down 1.5 years ago as I turned my attention primarily to powerpc64 > and to some extent arm*. That's very sad. I've been fixing some BROKEN_sparc64 ports in the early 2018 using QEMU. It was very slow, but worked fine overall. I forgot exactly which FreeBSD version I was able to boot. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190615134332.GA32655>