-
Notifications
You must be signed in to change notification settings - Fork 144
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
GLIBC errors #1317
Labels
Comments
Thanks for the report, and apologies for the delay in responding. I've got a patch to update our release script to include this. |
This next patch release will have binaries build with |
gcf-merge-on-green bot
pushed a commit
that referenced
this issue
Apr 15, 2024
🤖 I have created a release *beep* *boop* --- ## [1.65.1](https://togithub.com/googleapis/api-linter/compare/v1.65.0...v1.65.1) (2024-04-15) ### Bug Fixes * **ci:** build binaries with CGO_ENABLED=0 ([#1371](https://togithub.com/googleapis/api-linter/issues/1371)) ([f776eca](https://togithub.com/googleapis/api-linter/commit/f776ecaa0fbab579726120383139c13e9f57e479)), fixes [#1317](https://togithub.com/googleapis/api-linter/issues/1317) * ignore proto3_optional fields in oneof check ([#1370](https://togithub.com/googleapis/api-linter/issues/1370)) ([0d6e074](https://togithub.com/googleapis/api-linter/commit/0d6e0742603c377e86e6abbc557d6ff20e142a46)), fixes [#1323](https://togithub.com/googleapis/api-linter/issues/1323) --- This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by bazel-out/k8-opt- exec-ST-13d3ddad9198/bin/tools/api_linter.runfiles/api_linter/api-linter)
Environment details
Steps to reproduce
Based on this Go issue, I believe the builds should be run with
CGO_ENABLED=0
since I don't think API linter uses cgo.The text was updated successfully, but these errors were encountered: