What is happening with glibc and gcc packages?

Allan · 2022-02-09 23:20:35

agapito wrote:

I've installed the new toolchain and my computer hasn't exploded yet, I am not having any problems at the moment.
I could compile my custom kernel just fine, but other packages failed to compile throwing these kind of errors
/usr/bin/ld: /usr/lib/libx265.so.199: reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_create(unsigned long&, unsigned long)@GLIBCXX_3.4.21' not defined

Can you give an exact example of a package that fails like this? This seems to be in the realm of a partial update.

Edit: I can see this...

Allan · 2022-02-09 23:28:01

johnyan wrote:

Also the new toolchain doesn't move the --enable-install-libiberty to binutils. Do you think it's worth to open a bug report? I installed the new staging toolchain. so far no issue.

It is as if every improvement people provided patches for was ignored...

Edit: I am told this was intended "just to get the update" and other things will be merged in the coming weeks.

freswa · 2022-02-09 23:46:39

Hey people,
thank you for posting here. Your voice is heard and while compiling the toolchain this thread helped a lot!
I intentionally went for a fast release to have glibc 2.35 out rather soon than to make a lot of changes with the first release after months and a new maintainer.
I'm looking at the patches now and start running tests.

johnyan · 2022-02-09 23:58:09

Hey freswa, thank you so much for your work and contribution.

Allan · 2022-02-10 00:44:17

agapito wrote:

but other packages failed to compile throwing these kind of errors

/usr/bin/ld: /usr/lib/libx265.so.199: reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_create(unsigned long&, unsigned long)@GLIBCXX_3.4.21' not defined

Turns out that if libx265 is compiled with latest binutils (as the variant in [testing] is), then this is "fixed". Now to figure out why...

loqs · 2022-02-10 04:16:43

Allan wrote:

loqs wrote:
agapito wrote:
GLIBC: https://archlinux.org/packages/staging/x86_64/glibc/
Sadly with CET still enabled [1].
[1] https://lore.kernel.org/all/a7e59ae16e0 … intel.com/
Any chance you want to open a bug report with more explanation than a very long mailing list link?

https://bugs.archlinux.org/task/73708
Brief summary glibc upstream expected CET to be left off as it was by default until kernel support was finalized. Without kernel support it does not work, with a kernel supporting the current proposed interface it will not work as expected and can produce segfaults.

agapito · 2022-02-10 07:35:46

Allan wrote:

agapito wrote:
I've installed the new toolchain and my computer hasn't exploded yet, I am not having any problems at the moment.
I could compile my custom kernel just fine, but other packages failed to compile throwing these kind of errors
/usr/bin/ld: /usr/lib/libx265.so.199: reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_create(unsigned long&, unsigned long)@GLIBCXX_3.4.21' not defined
Can you give an exact example of a package that fails like this? This seems to be in the realm of a partial update.
Edit: I can see this...

obs-studio-git from AUR. I'm using the staging repo by the way.

EDIT: Manually rebuilding some packages from staging repo, made errors gone away.

Last edited by agapito (2022-02-12 15:40:23)

dogknowsnx · 2022-02-10 08:56:25

freswa wrote:

Hey people,
thank you for posting here. Your voice is heard and while compiling the toolchain this thread helped a lot!
I intentionally went for a fast release to have glibc 2.35 out rather soon than to make a lot of changes with the first release after months and a new maintainer.
I'm looking at the patches now and start running tests.

Thanks a lot! FWIW I've installed the toolchain from testing and compiled a couple small packages (termite, yambar-git, personal PKGBUILDS) without any issues - so far everything's working smoothly here...

Last edited by dogknowsnx (2022-02-10 08:57:17)

afader · 2022-02-12 18:31:27

Thanks to all for getting this into testing. If I install it however it doesn't quite work yet for my packages. Is there any way to trigger packages that need new glibc to reinstall or just be patient? I guess I could switch some distribution packages to -git versions and if they compile, great?

Edit: Got everything working, thanks all

Last edited by afader (2022-02-15 00:52:17)

Allan · 2022-02-13 01:30:58

afader wrote:

Thanks to all for getting this into testing. If I install it however it doesn't quite work yet for my packages. Is there any way to trigger packages that need new glibc to reinstall or just be patient? I guess I could switch some distribution packages to -git versions and if they compile, great?

"doesn't quite work" is the vaguest description of a problem... That gives us nothing to go on to fix your issues.

afader · 2022-02-13 22:02:43

Edit: Got everything working, thanks all

Last edited by afader (2022-02-15 00:52:33)

Zorbik · 2022-02-15 14:59:21

Looks like the core glibc package was updated last night. Thanks to the maintainers

ewaller · 2022-02-15 15:18:11

And with that, I shall close this thread.

Arch Linux

#151 2022-02-09 23:20:35

Re: What is happening with glibc and gcc packages?

#152 2022-02-09 23:28:01

Re: What is happening with glibc and gcc packages?

#153 2022-02-09 23:46:39

Re: What is happening with glibc and gcc packages?

#154 2022-02-09 23:58:09

Re: What is happening with glibc and gcc packages?

#155 2022-02-10 00:44:17

Re: What is happening with glibc and gcc packages?

#156 2022-02-10 04:16:43

Re: What is happening with glibc and gcc packages?

#157 2022-02-10 07:35:46

Re: What is happening with glibc and gcc packages?

#158 2022-02-10 08:56:25

Re: What is happening with glibc and gcc packages?

#159 2022-02-12 18:31:27

Re: What is happening with glibc and gcc packages?

#160 2022-02-13 01:30:58

Re: What is happening with glibc and gcc packages?

#161 2022-02-13 22:02:43

Re: What is happening with glibc and gcc packages?

#162 2022-02-15 14:59:21

Re: What is happening with glibc and gcc packages?

#163 2022-02-15 15:18:11

Re: What is happening with glibc and gcc packages?

Board footer