Bug 258378 - [exp-run] Update GCC_DEFAULT from 10 to 11
Summary: [exp-run] Update GCC_DEFAULT from 10 to 11
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Ports Framework (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Port Management Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-08 22:21 UTC by Gerald Pfeifer
Modified: 2021-09-20 07:17 UTC (History)
1 user (show)

See Also:
gerald: merge-quarterly-
gerald: exp-run?


Attachments
Patch to Mk/bsd.default-versions.mk (381 bytes, patch)
2021-09-08 22:21 UTC, Gerald Pfeifer
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Gerald Pfeifer freebsd_committer 2021-09-08 22:21:27 UTC
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...
Comment 1 Antoine Brodin freebsd_committer 2021-09-19 07:02:16 UTC
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
Comment 3 Gerald Pfeifer freebsd_committer 2021-09-20 07:11:27 UTC
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.
Comment 4 Antoine Brodin freebsd_committer 2021-09-20 07:17:35 UTC
(In reply to Gerald Pfeifer from comment #3)
Those hosts are ipv6 only.
You can reach them from freefall for instance.