-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
add aarch64-unknown-openbsd support #46760
Conversation
@bors: r+ |
📌 Commit 6b184b0 has been approved by |
⌛ Testing commit 6b184b09ce1c186e5a2ed610f21d5f44dd5ec43b with merge 3a97ba4b02384b183ab370e50338f943fc7124b0... |
💔 Test failed - status-travis |
errors are due to libc code for freebsd:
it contains code that seems to be not usable in staged api:
@alexcrichton what should be the correct way to deal with that ? I assume it should be corrected in libc ? but how ? |
Is the problem that rust-lang is using those deprecated constants, or reexporting them? |
@asomers I found no usage of this constants neither explicit reexport. |
@semarie want to send a PR to libc to remove those attributes? |
- make liblibc to point to libc with aarch64-unknown-openbsd - make c_char (in std::os::raw) to point to right value
6b184b0
to
8c7b093
Compare
ok, I updated my branch to include the |
@bors: r+ |
📌 Commit 8c7b093 has been approved by |
add aarch64-unknown-openbsd support - make liblibc to point to libc with aarch64-unknown-openbsd - make c_char (in std::os::raw) to point to right value r? @alexcrichton currently, I have only tested in crosscompilation environement (openbsd x64_64 -> openbsd aarch64). it produces valid binaries.
r? @alexcrichton
currently, I have only tested in crosscompilation environement (openbsd x64_64 -> openbsd aarch64). it produces valid binaries.