-
Notifications
You must be signed in to change notification settings - Fork 1.1k
s390x-musl: define O_LARGEFILE constant #3262
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
Conversation
r? @JohnTitor (rustbot has picked a reviewer for you, use r? to override) |
I agree that libc should probably expose the value (so code that checks if it is set in a bitmask works?) but I think it's set to |
doesn't seem to be (note aarch64, for instance), from musl source:
ok, that seems much more thorough as a unification project. perhaps you'd like to also add these constants into that too? although in this case, these don't actually seem consistent for all 32 or all 64 bit widths.. |
my initial motivation is that rust 1.70 built on s390x musl now fails without this exposed. i'm not exactly sure why, as the failure is from perhaps because of some doc feature.. but it indeed is harmless to expose, so hotpatching it for vendor/libc worked fine. |
Huh, there's more divergence than I expected, don't worry about the unification then! |
no worries, thanks for the review! always nice to see people working on these interfaces too :) |
Thanks! @bors r+ |
☀️ Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14 |
from https://git.musl-libc.org/cgit/musl/tree/arch/s390x/bits/fcntl.h?id=4b125dd408d54487dc8843b9553502aa0c4167f8#n16
it's a nop as noted in 75ac488, but afaik we should still expose the symbol(?)