-
Notifications
You must be signed in to change notification settings - Fork 117
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
Possible glibc issue on x86_64 linux systems #899
Comments
There a discussion here, explaining that for using statically linked binary you need the same version of glibc. |
Happy debugging folks, if this can help.. :) |
We are trying to work out the best approach to this one as its a bit tricky. In the meantime if you have this issue you can always either:
|
Yup don't worry, I picked the docker right away, I was just giving feedbacks in case it'd help ;) |
Currently working towards a solution here #921 |
We've found a performance regression as a result of our fix and we are continuing to investigate and will release a new version as soon as we can. #925 |
bearer_1.4.0_linux_amd64.tar.gz -> Works like a charm! ;) |
Description
Currently on linux it looks like we are seeing some segfaults with some users that have the
x86_64
instruction set. This is somewhat unexpected as we compile foramd64
here which should be compatibleuname -a
works:
does not work:
Related
https://stackoverflow.com/questions/75986529/bearer-scan-fails-to-run-for-react-project
The text was updated successfully, but these errors were encountered: