Date: Tue, 26 May 2020 22:55:30 +0000 From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 245511] lang/gcc9: build with base GCC on powerpc64 elfv1 Message-ID: <bug-245511-25139-TYf33Dxyua@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-245511-25139@https.bugs.freebsd.org/bugzilla/> References: <bug-245511-25139@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D245511 --- Comment #29 from Gerald Pfeifer <gerald@FreeBSD.org> --- (In reply to Piotr Kubaj from comment #22) > I don't want to open a new bug for that or reopen the old one. > > I'd like to get lang/gcc11-devel building because, as I wrote before, > it serves as CI-like port to make sure it builds. I know no port depends > on that, but you still added ARM patch :) Could you then patch PPC as wel= l? The Arm patch is an unfortunate example. It shows a local patch we are stuck with "forever" and anyone building from pristine upstream sources will get something not fully compatible. (And I have not added it, just svn cp-ed it again and again as part of the whole port whenever a new version came up.) GCC HEAD, which feeds lang/gcc11-devel, just made C++ 11 a requirement which means GCC 4.2 is out of the picture for real now. This renders the situati= on quite different, and in any case - yes, let's use this in a CI-like manner - in the sense of testing close to upstream and working to tackle things upstream. To summarize, let's focus on gcc9-devel and the gcc10/gcc10-devel ports with priority to ensure those are fine, since those are what our users will primarily run for the next year. And in parallel work upstream for anything that's needed for gcc11-devel. Thanks to weekly snapshots we'll quickly pick up any changes. --=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-245511-25139-TYf33Dxyua>