Created attachment 227774 [details] Patch to Mk/bsd.default-versions.mk With GCC 11.2 the GCC 11 series already is in it's second release and used by some Linux distributions like openSUSE Tumbleweed, so let's see to make that move on the FreeBSD side as well. Now that we have the infrastructure in place the patch for this switch itself is most straightforward. The question is how many broken ports we carry around...
New failure logs on 12.2 amd64: http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/alliance-5.1.1_2.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/elfutils-0.179.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/plexil-4.5.0_1.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/ypsilon-0.9.6.3_11.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/sage-math-9.2_18.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/avidemux-2.7.6_2.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/elmerfem-8.4.20200708_2.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/massxpert-3.6.1_1.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/nwchem-7.0.2.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/edk2-fvp-g202102.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/edk2-rpi3-g202102.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/edk2-rpi4-g202102.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/edk2-xen-x64-g202102.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/edk2-macchiatobin-g202102.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/pesign-0.110_8.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/uefi-edk2-bhyve-g20210226,2.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/uefi-edk2-qemu-i386-g20191122.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2021-09-18_18h41m21s/logs/errors/uefi-edk2-qemu-x86_64-g20191122.log
New failure logs on 12.2 i386: http://pb2.nyi.freebsd.org/data/122i386-default-foo/2021-09-18_18h41m24s/logs/errors/polygraph-4.13.0_2.log http://pb2.nyi.freebsd.org/data/122i386-default-foo/2021-09-18_18h41m24s/logs/errors/alliance-5.1.1_2.log http://pb2.nyi.freebsd.org/data/122i386-default-foo/2021-09-18_18h41m24s/logs/errors/plexil-4.5.0_1.log http://pb2.nyi.freebsd.org/data/122i386-default-foo/2021-09-18_18h41m24s/logs/errors/ypsilon-0.9.6.3_11.log http://pb2.nyi.freebsd.org/data/122i386-default-foo/2021-09-18_18h41m24s/logs/errors/avidemux-2.7.6_2.log http://pb2.nyi.freebsd.org/data/122i386-default-foo/2021-09-18_18h41m24s/logs/errors/aircrack-ng-1.5.2_2.log http://pb2.nyi.freebsd.org/data/122i386-default-foo/2021-09-18_18h41m24s/logs/errors/mpich2-1.5_15,5.log http://pb2.nyi.freebsd.org/data/122i386-default-foo/2021-09-18_18h41m24s/logs/errors/massxpert-3.6.1_1.log http://pb2.nyi.freebsd.org/data/122i386-default-foo/2021-09-18_18h41m24s/logs/errors/fluxengine-572.log http://pb2.nyi.freebsd.org/data/122i386-default-foo/2021-09-18_18h41m24s/logs/errors/pesign-0.110_8.log
Thank you, Antoine. How does one access the failure logs? Both http://package18.nyi.freebsd.org and http://pb2.nyi.freebsd.org don't work (resolve at the DNS level) for me.
(In reply to Gerald Pfeifer from comment #3) Those hosts are ipv6 only. You can reach them from freefall for instance.
(In reply to Antoine Brodin from comment #4) Hello, I am about to create PRs to fix all those ports. I successfully reach the links using freefall as a proxy, however all logs from comment #2 seems to have been removed. Indeed, for all of them I get the following response: <html> <head><title>404 Not Found</title></head> <body> <center><h1>404 Not Found</h1></center> <hr><center>nginx/1.20.2</center> </body> </html> Could you please check if the logs still exist and, if not, run the exp-run for i386 again? Thanks.
I have created all the PRs for the amd64 architecture.
Looks of good process driven by salvadore@. Thank you!
Antoine / portmgr@, given the amount of changes and the timing of the original run, would you mind doing another exp- run? Or should we go ahead and bump GCC_DEFAULT as is? Thank you! (There's only two uefi-edk2* ports left we are aware of which can be addressed with USE_GCC=10 if necessary.)
New failure logs: http://package22.nyi.freebsd.org/data/130amd64-default-foo/2022-05-26_19h07m28s/logs/uefi-edk2-qemu-x86_64-g20191122.log http://package22.nyi.freebsd.org/data/130amd64-default-foo/2022-05-26_19h07m28s/logs/uefi-edk2-qemu-i386-g20191122.log
More failure logs on i386: http://package23.nyi.freebsd.org/data/130i386-default-foo/2022-05-26_19h07m39s/logs/errors/polygraph-4.13.0_2.log http://package23.nyi.freebsd.org/data/130i386-default-foo/2022-05-26_19h07m39s/logs/errors/aircrack-ng-1.5.2_3.log http://package23.nyi.freebsd.org/data/130i386-default-foo/2022-05-26_19h07m39s/logs/errors/mpich2-1.5_15,5.log http://package23.nyi.freebsd.org/data/130i386-default-foo/2022-05-26_19h07m39s/logs/errors/fluxengine-572.log http://package23.nyi.freebsd.org/data/130i386-default-foo/2022-05-26_19h07m39s/logs/errors/onlyoffice-documentserver-7.1.0.215.log
(In reply to Antoine Brodin from comment #10) Thanks. I am going to deal with all these logs.
All the needed new bugs have been created and the only remaining old bug has been updated.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=cad2f66a384d74cffa870d978722e6fd579c7d2f commit cad2f66a384d74cffa870d978722e6fd579c7d2f Author: Gerald Pfeifer <gerald@FreeBSD.org> AuthorDate: 2022-06-27 17:57:18 +0000 Commit: Gerald Pfeifer <gerald@FreeBSD.org> CommitDate: 2022-06-27 17:59:07 +0000 Mk/bsd.default-versions.mk: Switch default GCC from 10 to 11 Update GCC_DEFAULT, the default version of GCC as pulled in via USE_GCC=yes and a myriad of other ways from GCC 10 (10.3 currently) to GCC 11 (11.3 currently). PR: 258378 Tested by: antoine (exp-runs) Thanks to: salvadore (for heavy lifting across the board) Mk/bsd.default-versions.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
An the update is live, in time for the next quarterly branch. Thanks for all the work, Lorenzo!
^Triage: Assign to user that resolved the issue You're welcome Gerald, it's a pleasure.