AngryPhantom

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?

@JamiKettunen Ok, thanks!

@oreo639 I saw this. I mean what Arch has to do with glibc which is [GNU.org](https://www.gnu.org/software/libc/) ? Does Void ship glibc patched by Arch? Why if so?

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

And what about backward [compatibility](https://developers.redhat.com/blog/2019/08/01/how-the-gnu-c-library-handles-backward-compatibility)?

> 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](http://deb.debian.org/debian/pool/main/g/glibc/glibc_2.31-13+deb11u4.debian.tar.xz) does to it? Arch is a school...

@sanyam8929 I used the 5.7.6.1 branch with the patch mentioned above and it works with no issues for me. But the original code should be fixed and updated.

@LevitatingBusinessMan Nope. There is a link to the [make.log](https://pastebin.com/raw/JLVcM6Ff) in my post.

I can confirm this. But even disabling **Use psutils** doesn't help in my case. Distro: Void Linux (64bit glibc). All dependencies are satisfied, `sensors` command is working. Bashtop version is...

Guys, I'm not sure if it's related but I've run **hdrcopy** by mistake today (instead of another command in bash) and just found out what it is (a part of...