On Sat, 26 Oct 2019, Konstantin Belousov wrote: >>> It is very strange. Are gcc 9 or 8 affected ? >> gcc 8 and 9 are affected too. > Then this is a completely different cause then I guessed below, and I think > I know why. All of 8/9/10 gcc ports have support for multiarch, and the > error must happen for gcc or xgcc invocation with -m32, am I right ?
Here is what I got in terms of just being bombarded with build failure reports across the board, the two below being for lang/gcc8: Date: Sat, 26 Oct 2019 11:46:37 GMT Subject: [package - head-amd64-default][lang/gcc8] Failed for gcc8-8.3.0_3 in build Log URL: http://beefy19.nyi.freebsd.org/data/head-amd64-default/2019-10-26_10h54m41s/logs/gcc8-8.3.0_3.log Build URL: http://beefy19.nyi.freebsd.org/build.html?mastername=head-amd64-default&build=2019-10-26_10h54m41s -and- Date: Sat, 26 Oct 2019 12:59:10 GMT Subject: [package - head-amd64-pcb-default][lang/gcc8] Failed for gcc8-8.3.0_3 in build Log URL: http://beefy19.nyi.freebsd.org/data/head-amd64-pcb-default/2019-10-26_12h17m09s/logs/gcc8-8.3.0_3.log Build URL: http://beefy19.nyi.freebsd.org/build.html?mastername=head-amd64-pcb-default&build=2019-10-26_12h17m09s Indeed I see -m32 in the last invocation of xgcc here in both case. Gerald _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "[email protected]"
