void-packages icon indicating copy to clipboard operation
void-packages copied to clipboard

Published 20 hours ago • verified publisher icon void-linux

glibc: update to 2.34.

Open ericonr opened this issue 3 years ago • 5 comments

From release notes:

Starting with glibc 2.34, the shared objects are installed under their ABI sonames directly, without symbolic links.

Therefore, we have to rename many of the nostrip entries.

Also from release notes:

all functionality formerly implemented in the libraries libpthread, libdl, libutil, libanl has been integrated into libc.

Therefore, we can remove these libraries from the nostrip list entirely.

General

Have the results of the proposed changes been tested?

  • [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
  • [ ] I generally don't use the affected packages but briefly tested this PR

ericonr avatar Aug 05 '21 04:08 ericonr

Could this be bumped to 2.35 which released about 2 weeks ago?

JamiKettunen avatar Feb 15 '22 06:02 JamiKettunen

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.

github-actions[bot] avatar May 31 '22 02:05 github-actions[bot]

Arch has patched glibc heavily since 2.35 release so idk how I feel about pushing it. https://github.com/archlinux/svntogit-packages/commits/packages/glibc/trunk

ericonr avatar Jun 05 '22 21:06 ericonr

Might be worth changing the PR title to reflect the version change; easier to search for that way (I almost didn't find this)

Seltyk avatar Jul 30 '22 16:07 Seltyk

glibc 2.36 is out. (the only patch Arch has for that so far is just a workaround for an Easy Anticheat issue)

oreo639 avatar Aug 13 '22 06:08 oreo639

Any plans updating it, guys? It's still 2.32 which is two years old. And what does Arch have to do with glibc btw?

AngryPhantom avatar Sep 22 '22 13:09 AngryPhantom

This should probably be closed; it seems glibc update (to 2.36) will be done as a part of #34902 (gcc: update to 12.2.0.) unless I'm mistaken.

JamiKettunen avatar Sep 22 '22 13:09 JamiKettunen

@JamiKettunen Ok, thanks!

AngryPhantom avatar Sep 22 '22 14:09 AngryPhantom

AngryPhantom:

And what does Arch have to do with glibc btw?

ericonr:

Arch has patched glibc heavily since 2.35 release so idk how I feel about pushing it.

oreo639 avatar Sep 23 '22 01:09 oreo639

@oreo639 I saw this. I mean what Arch has to do with glibc which is GNU.org ? Does Void ship glibc patched by Arch? Why if so?

AngryPhantom avatar Sep 23 '22 08:09 AngryPhantom

No, it's just more of a learn from other's mistakes deal (look what bugs others have run into and what patches other distros are using so you can avoid breakages/regressions, ofc not all of those patches will be useful and some are distro-specific tweaks or just wrong, but at least you can get an idea).

oreo639 avatar Sep 23 '22 08:09 oreo639

@oreo639 Oh, thanks for the answer (and your patience). Didn't know that glibc is that buggy, jeez :(

AngryPhantom avatar Sep 23 '22 08:09 AngryPhantom

And what about backward compatibility?

AngryPhantom avatar Sep 23 '22 11:09 AngryPhantom

Arch has patched glibc heavily since 2.35 release so idk how I feel about pushing it. https://github.com/archlinux/svntogit-packages/commits/packages/glibc/trunk

Have you seen what Debian does to it? Arch is a school kid compared to Debian...

AngryPhantom avatar Sep 23 '22 11:09 AngryPhantom

And what about backward compatibility?

Usually it's fine. That doesn't mean issues can't occasionally slip through the cracks.

Have you seen what Debian does to it? Arch is a school kid compared to Debian...

It was just an example.

oreo639 avatar Sep 23 '22 16:09 oreo639