-
Notifications
You must be signed in to change notification settings - Fork 49
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
Missing fcntl.h headers when compiling rust build scripts #29
Comments
I guess it is building it in a different directory, not at the root of the bazel sandbox? Edit: check with Anyhow, this all linker-header hackery will be removed after ziglang/zig#15101 is merged. |
It seems to be running under
|
Also, another target we're building (jemalloc) uses
From the issue you've linked this seems to be related ( |
Yes, You are welcome to dig in and understand what the problem is (I will accept a patch that adds a test case and fixes it), or, in the meanwhile, run on glibc 2.34+ and get back to your desired glibc version when the problem is fully resolved with #29 (comment) |
@motiejus whats the next steps now that ziglang/zig#15101 is merged upstream? |
Upgrade the Zig SDK and remove all of the afore-mentioned hacks from bazel-zig-cc. I am on PTO until 2023-04-17 though -- feel free to pick it up or wait a week until I get back. |
Hi,
I've started looking into using
bazel-zig-cc
as a replacement forhttps://github.com/grailbio/bazel-toolchain
.Most stuff builds correctly (including numerous c deps that we have).
We are targeting libc 2.27, which seems to require a workaround.
However a build script for ring seems to not be able to find the
fnctl
headers, which wasn't a problem when we were using the llvm toolchain with a sysroot.I've tried to skim the toolchain definitions here, but it seems to be passing the correct include flags. Is there anything else that you may be aware that can cause this?
Thanks for this amazing project, it is compelling because it is so much lighter compared to the 500mb llvm prebuild binaries!
The text was updated successfully, but these errors were encountered: