-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
bear fails with erro #275145
Comments
#238531 this fix gets bear working for me fwiw |
This is still happening for me, using 23.11 or unstable. |
@laggron42 looks like the backport is still open. The patch that fixes the problem hasn't made its way from master into 23.11 or unstable. #279035 (comment) |
@DieracDelta Thanks for your answer! I have pulled from master, but the problem still happens for me:
The output of Output of
|
Ack, yeah it's broken for me too (with the same error). Not sure how to fix that... |
So, it's a mismatch between the glibc in nix-23.11 and nixos-unstable/master. If I rebuild my own config with |
Closing because it's due to nixpkgs versioning mismatch, and works on unstable. |
Still doesn't work for me. Is there some requirement that that Bear be built against an older version of glibc than what you run it with? In that case, I may need to pin an older version since I'm running on CentOS 7 with glibc 2.17. Or maybe I just need to set up the environment so bear dynamically links against a glibc from the nix store at runtime? I don't know bear internals enough to know how it interacts with the program being wrapped, and whether their glibc versions need to be compatible. I'm still getting errors like:
|
Describe the bug
bear is unable to produce compile_commands.json, fails with GLIBC error
Steps To Reproduce
Steps to reproduce the behavior:
executing
bear -- make all
inside a nix results in the following error/usr/bin/env: /lib/x86_64-linux-gnu/libc.so.6: version 'GLIBC_2.38' not found (required by /nix/store/dghjv6hfz0s0z4kffa5ahyw2mhp79215-gcc-12.3.0-lib/lib/libstdc++.so.6)
Notify maintainers
@babariviere
@alyssais
Metadata
The text was updated successfully, but these errors were encountered: