Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installing on RHEL-8.9 fails - "nothing provides libstdc++.so.6(GLIBCXX_3.4.26)(64bit)" #2052

Open
dsommers opened this issue Oct 8, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@dsommers
Copy link

dsommers commented Oct 8, 2024

This was already resolved once, in issue #1760 but has re-appeared once again.

# yum update
Updating Subscription Management repositories.
download.vscodium.com                                                                          1.5 kB/s | 833  B     00:00    
Error: 
 Problem: cannot install the best update candidate for package codium-1.92.2.24228-el8.x86_64
  - nothing provides libm.so.6(GLIBC_2.29)(64bit) needed by codium-1.94.0.24281-el8.x86_64 from gitlab.com_paulcarroty_vscodium_repo
  - nothing provides libstdc++.so.6(GLIBCXX_3.4.26)(64bit) needed by codium-1.94.0.24281-el8.x86_64 from gitlab.com_paulcarroty_vscodium_repo
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
# 

Desktop (please complete the following information):

@dsommers dsommers added the bug Something isn't working label Oct 8, 2024
@dsommers
Copy link
Author

dsommers commented Oct 8, 2024

This issue also appeared with codium-1.93.1.24256-el8.x86_64

@daiyam
Copy link
Member

daiyam commented Oct 8, 2024

Yes, since 1.93, VSCodium uses node-20 which requires glibc-2.29. I didn't expect to affect el8.
The move is due to that I wasn't able to pack the app with node-16 (if I remember correctly due to electron).
But reh and reh-web are still shipping with node-16.

You could use our AppImage (not available in 1.94, yet) or our flatpak.

So I will have to rename el8 to el9...

@dsommers
Copy link
Author

dsommers commented Oct 8, 2024

Okay, so I have tried the flatpak in the past ... and that sandboxing didn't work well with clangd at all - so lots of the IDE experience was lost. I can give the AppImage a try, but I'm not that happy about that approach - on large applications it takes considerably longer to start the app and it adds tons of various mount bindings.

But I do see that RHEL-8.9 does provide a nodejs:20 module.

# yum module reset nodejs
[...]
# yum module enable nodejs:20
[...]
# yum install nodejs
[...]
# node --version
v20.16.0
# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.10 (Ootpa)

@dsommers
Copy link
Author

dsommers commented Oct 8, 2024

I now see that I'm running RHEL-8.10, not 8.9 as indicated. But that shouldn't make a big difference either way.

@daiyam
Copy link
Member

daiyam commented Oct 8, 2024

Node itself isn't necessarily the issue since unofficial builds support glibc-2.17 (https://unofficial-builds.nodejs.org/download/release/) but the libraries used like electron, chromium or node modules with native binaries.

I agree flatpak and AppImage aren't ideal for an IDE.

@OmniBlade
Copy link

Upstream still appears to support RHEL8, can you not emulate the way they build and pack the app?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants