Update glibc to 2.37

[The-King-of-Toasters]

Closes #12808
Closes #12809
Closes #14798

See also: ziglang/glibc-abi-tool#4.

[BratishkaErik]

IIRC you said that you will jump straight to glibc 2.37, skipping two previous versions. Should we really mark two first issues as resolved then? IMHO they should stay as "not resolved yet"

[The-King-of-Toasters]

The process involves copying over all the new sources/headers, so the only benefit would be to bisect any build failures (which I'm probably going to have to do anyway judging by the CI...)

[motiejus]

For the sake of future maintainability please update lib/libc/glibc/README.md with the new commit hashes. Since this will likely be rebased, it's probably OK to do separately though.

Also, I find it easier to apply out-of-tree patches when they are separate commits instead of having a single larger one bundled. Up to you — but consider it.

[motiejus]

Also, I find it easier to apply out-of-tree patches when they are separate commits instead of having a single larger one bundled. Up to you — but consider it.

I take it back. With commits like #15573 it would become a mess quickly.

[andrewrk]

Closing this for multiple reasons:

• failing CI checks
• no action in months
• a core team member must do the glibc update process for security reasons