-
Notifications
You must be signed in to change notification settings - Fork 4.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
Bazel 3.7.0 can't be compiled on Alpine linux #12460
Comments
@kigero Sorry for that. I'll see that we revert this part or fix it in a way that works with non-glibcs. |
Same problem with bazel 4.0 and musl. This fix seems fairly straightforward, other projects seem to be implementing too: https://git.sailfishos.org/mer-core/profiled/merge_requests/5/diffs I've successfully built Bazel by adding the snippet from the above push to linux-sandbox-pid1.cc as suggested by kigero. I don't know much about Java, but if there are any tests you'd like me to run on my musl system to verify that it works correctly, please let me know - it's a real shame that such a small thing is preventing musl support. |
@foopub Do you want to send us a PR that fixes this (the diff that you linked seems fine to be)? Please ping me in the PR and I can import it asap. |
This allows us to build Bazel on Linux systems which use a C standard library that does not include this macro, like Alpine Linux (which uses musl). Fixes #12460. PiperOrigin-RevId: 374873483
This allows us to build Bazel on Linux systems which use a C standard library that does not include this macro, like Alpine Linux (which uses musl). Fixes bazelbuild#12460. PiperOrigin-RevId: 374873483
Description of the problem / feature request:
Bazel 3.7.0 can't be compiled on Alpine linux; I get the following error:
It seems that TEMP_FAILURE_RETRY is only available on GNU libc, where Alpine uses musl libc. The last Bazel version I tried on Alpine was 3.5.0 and that was compiling/running fine.
What operating system are you running Bazel on?
Alpine linux, 3.13.0_alpha20200917. Running within docker using the
alpine:edge
tag.Have you found anything relevant by searching the web?
linux-sandbox-pid1.cc
file, but this is not my area of expertise so I can't tell if it's actually doing what it's supposed to do, or if it just looks like it is.The text was updated successfully, but these errors were encountered: