gcc: update to 12.2.0.

[oreo639]

[ci skip]

Edit: this PR had been updated for gcc 12.2.0

There are lists of failing builds here: #39809, #39960

I tested this PR with glibc and after updating glibc, it seems to work fine.
I also tested this PR with x86_64-musl, and it appears to run fine in a musl chroot, and recompiling and installing musl with gcc 12 doesn't appear to result in any issues. (more testing is needed)

Please let me know if there are any issues.

I compiled base-system and base-chroot on x86_64-glibc and x86_64-musl to ensure that compiles and it appears to work fine.

I tested some of the cross compilers and after some debugging with the help of CameronNemo, we figured out the issue.
The cross compilers are built with nopie=yes (specified in environment/build-style), which causes issues with glibc 2.35+ which uses PIE by default.
gcc always builds itself as nopie.
I added a workaround to common/build-style/void-cross but if you have any other recommendations on how to handle it, feel free to let me know.

This PR also updates glibc to 2.36:
https://sourceware.org/glibc/wiki/Release/2.36

Necessary to fix previously existing build failures (unrelated to this PR):

• firefox-esr firefox-esr: update to 102.3.0. #39677
• gupnp gupnp: needs docbook-xsl in hostmakedepends #38844

Known packages that need to be fixed/updated for glibc 2.36:

• samba samba: fix build for glibc 2.36 #38700
• qemu qemu: fix build for glibc 2.36 #38769
• llvm llvm12: fix build for glibc 2.36 #38694
• m4 m4: update to 1.4.19. #33730
• btrfs-progs btrfs-progs: update to 5.19. #38778
• ntp ntp: fix build with glibc 2.34 #38772
• libarchive libarchive: fix build for glibc 2.36 #38773
• boost boost: fix build for glibc 2.34 #38784
• chroot-grep chroot-grep: update to 3.7. #38785
• plymouth plymouth: update to 22.02.122. #38821
• fuse fuse: fix build for glibc 2.34 #38827
• libostree libostree: fix build for glibc 2.36 #38828
• libvirt libvirt: fix build for glibc 2.36 #38842
• syslinux syslinux: fix build for glibc 2.36 #38876
• efivar efivar: fix build for glibc 2.36 #38874
• gpgme gpgme: fix returning incorrect error codes #38825

Known packages that needed to be fixed/updated for gcc12:

• openssh openssh: relax warnings for gcc12 #38849
• xf86-video-vmware xf86-video-vmware: fix build for gcc12 #38847
• doxygen doxygen: fix build for gcc 12 #38846
• firefox-esr firefox-esr: update to 102.3.0. #39677
• libproxy libproxy: update to 0.4.18. #38818
• exempi exempi: update to 2.6.2. #38820
• openjdk7-bootstrap openjdk7-bootstrap: fix build for gcc12 #38822
• libunique1 libunique1: relax warnings for gcc12 #38848 or libunique{,1}: remove package #38873
• libwpd libwpd: fix build for gcc12 #38878
• cglm cglm: update to 2.8.5. #39748
• coreboot-utils coreboot-utils: update to 4.17. #39749
• apl apl: disable werror #39750
• igt-gpu-tools igt-gpu-tools: fix buffer overflow warning #39780

Needs to be fixed/updated for binutils:

• grub grub: fix build for binutils 2.36 #38875
• linux-tools linux-tools: fix build for binutils 2.39 #38877
• kcov kcov: fix build with binutils 2.39 #39291

ISO packages verified:

• base system
• base chroot
• gnome
• xfce
• mate
• cinnamon
• enlightenment
• kde
• lxde
• lxqt

You can test the ISOs here:
https://drive.google.com/drive/folders/1ix92CYSLUP-KWjLxltdgG4e8Nu2JCY5n?usp=sharing

Testing the changes

• I tested the changes in this PR: briefly

Local build testing

• I built this PR locally for my native architecture, (x86_64-glibc)
• I built this PR locally for these architectures (if supported. mark crossbuilds):
  • x86_64-musl

[dkwo]

I was getting a bunch of WARNING: usr/lib/*.so should be in -devel package as well as

=> WARNING: libada-11.2.1git20211128_1: libgnarl-11.so not found in common/shlibs!
=> WARNING: libada-11.2.1git20211128_1: libgnat-11.so not found in common/shlibs!
=> WARNING: gcc-11.2.1git20211128_1: libcp1plugin.so.0 not found in common/shlibs!

[oreo639]

=> WARNING: libada-11.2.1git20211128_1: libgnarl-11.so not found in common/shlibs!
=> WARNING: libada-11.2.1git20211128_1: libgnat-11.so not found in common/shlibs!

Thank you for pointing that out, fixed.

=> WARNING: gcc-11.2.1git20211128_1: libcp1plugin.so.0 not found in common/shlibs!

libcp1plugin.so.0 is in the current gcc 10 package and isn't in shlibs, so I assume that isn't an issue since nothing depends on it.

Same for all of the WARNING: usr/lib/*.so should be in -devel package afaict, so unless the maintainers think it is an issue, it probably isn't a big deal.

[lane-core]

@oreo639 is there any way that I can assist this effort?

[oreo639]

Not that I am aware of at the moment. If the maintainers want me to make any changes they can let me know. If they want to use it as a reference for their own gcc 11.2 port, they can do so.

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.

[motorto]

@oreo639: could you bump this so that this work isn't lost ? I will try to build on my x86_64-musl system and report back.

And maybe bump to 12.1.0 ?

[lane-core]

👀 🥇

[sug0]

Thank you for your hard work! Looks like the patchset can be used to build a gcc 12 toolchain now. Any current blockers on the merge?

[lane-core]

what a nice surprise running xbps-install -Su today, thank you for all the hard work @oreo639!!

[oreo639]

Np. Also, thank you paper42, sgn, leahneukirchen, and Johnnynator.

[TeusLollo]

Indeed. Thanks to @oreo639 and to the rest of the gang.

By the next gcc/glibc update, I hope I'll be knowledgeable enough of the xbps build system to help at least with testing/pull requests (Still too much of a newbie at distro maintenance, for now I'm mostly a bug reporter/fix identifier)

[CameronNemo]

Why was this done?

[oreo639]

glibc has a release branch where patches go to including several critical ones.
https://github.com/bminor/glibc/tree/release/2.36/master
paper didn't want me to include the branch as a patch (like what debian does) since the patch is enormous.
So we generated a tarball from the release branch using make dist. (Fedora does this and Arch just uses git)
It was generated from the following commit:
bminor/glibc@0f90d62

The patchver is the output of git describe: <ncommit>-g<commit-hash>
Where ncommit is the number of commits between the release branch and the release tag.

It was also supposed to get uploaded to https://repo-default.voidlinux.org/distfiles/ but no one has done that yet so it is still pointing to paper's server.