-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Neovide failes in mixed glibc configuration #168769
Comments
can we close this ? |
Would be my call, too since mixed glibc is normally out for trouble. |
Would be nice if there was some workaround out there first (something like overriding the glibc used?). At the end of the day, this issue means that I'm having to run an old and somewhat buggy version of neovide, whereas unstable has a much more solid one. Nevertheless, I understand that this is tricky and likely won't have a definite solution. |
Just wondering, if there is a convenient way to use the package source in unstable but evaluate using other channels? The way I'm doing this right now is to copy the file |
I close this issue, since it is more general issue. |
Describe the bug
If you run NixOS 21.11 which uses glibc version 2.33 and want to run neovide from nixon-unstabled which is compiled with glibc version 2.34, then neovide failes to start.
Glibc 2.34 was introduced with #133431
Steps To Reproduce
Expected behavior
The application starts.
Notify maintainers
I am the maintainer.
Metadata
The text was updated successfully, but these errors were encountered: