Tie together loose ends for automated native builds #124
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
headius
force-pushed
the
auto-native-builds
branch
6 times, most recently
from
db88ff2 to
108d7ac
Compare
headius
force-pushed
the
auto-native-builds
branch
from
108d7ac to
0fd4275
Compare
|
After some tweaks and hooking up to our MacStadium M1 instance the Darwin build appears to be working. |
These were built automatically using the workflows in jnr#124.
headius
force-pushed
the
auto-native-builds
branch
from
01cbdf2 to
4c79fb1
Compare
|
I attempted to add the other platforms supported by the debian image, but only riscv64 appears to have worked. The ppc64el build failed with a trap error (possibly fixed by https://gitlab.com/qemu-project/qemu/-/issues/588 or the related patches listed there, not yet in a release) and the mip64el build fails deep inside openjdk IO/thread-wrangling code (my email to the mips openjdk list should eventually show up here: https://mail.openjdk.java.net/pipermail/mips-port/2020-April/thread.html). So I will add riscv64 to the supported platform list but the other ones need extra help. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have workflows in place for Windows, macOS, and Linux, but not everything is hooked up to our process for pulling those automated builds down and inserting them back into releases. This PR will try to do that.
The workflows are in the usual place,
.github/workflows.At the moment the Linux builds are working for arm (v7ish?), arm64 (arm64v8/aarch64), i386, amd64 (x86_64), and s390x. macOS and Windows builds are in place but not fully working. No builds for any BSDs or Solaris.
Shipping in our archive native binaries currently (checked builds currently work):
Note there is also an "armv5" build for Linux that does not have a home, since we do not differentiate ARM architectures to that level of granularity (we only have "arm" and "aarch64" as endpoints right now).