On Tue, 23 Apr 2019 16:52:57 +0100, Stuart Henderson wrote: > On 2019/04/23 17:14, Christian Weisgerber wrote: > > With everybody eager to switch ports-gcc to gcc8, I'm still a bit > > hazy about which architectures gcc8 is actually known to work on. > > To the best of my knowledge: > > > > should be fine > > aarch64 already switched > > amd64 successful bulk build > > powerpc successful partial build > > sparc64 successful partial build > > > > optimistic > > hppa existence of adastrap 8.3.0 suggests working compiler > > mips64 existence of adastrap 8.2.0 suggests working compiler > > mips64el == mips64? > > > > don't know > > arm ? > > alpha ? (don't care) > > > > known bad > > i386 marked BROKEN > > > > -- > > Christian "naddy" Weisgerber [email protected] > > From the last snaps: > > -rw-rw-r-- 1 openbsd openbsd 23870613 Apr 21 09:53 aarch64/gcc-8.3.0.tgz > -rw-rw-r-- 1 openbsd openbsd 28096948 Apr 21 18:07 amd64/gcc-8.3.0.tgz > -rw-rw-r-- 1 openbsd openbsd 27137929 Feb 25 05:54 arm/gcc-8.2.0p0.tgz > -rw-rw-r-- 1 openbsd openbsd 25484157 Apr 6 14:04 mips64/gcc-8.2.0p2.tgz > -rw-rw-r-- 1 openbsd openbsd 27639770 Mar 31 22:07 powerpc/gcc-8.2.0p2.tgz > -rw-rw-r-- 1 openbsd openbsd 22927965 Mar 19 14:44 sparc64/gcc-8.2.0p2.tgz > > I'll try removing the BROKEN-i386 marker and building there in case anything > changed in the 8.3.0 update. > >
Won't build, but I'm on it.
