1.6.5 Unable to build on !ppc64le !riscv64 !s390x
Hey there,
This is just to report that the latest release does not build for those arches, on Alpine Linux. This has been tested further by Celeste. She tried building the previous version with the latest Gradle version, and she succeed. So probably something is wrong with some dis4irc dependencies bumps?
full context here: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/84712#note_511105
Thanks,
Hello,
I must admit that I've never tried to build this for anything other than amd64 and aarch64.
I do have a riscv64 board and I can confirm the riscv64 failure. This is indeed a regression from v1.6.4. The other platforms I would need to set up emulation to test independently but hopefully it's the same cause as riscv64.
These are the relevant logs from Alpine's runners (just so I don't have to go look them up over and over):
ppc64le:
FAILURE: Build failed with an exception.
* What went wrong:
java.lang.ExceptionInInitializerError (no error message)
> Unknown hardware platform: ppc64le
riscv64:
FAILURE: Build failed with an exception.
* What went wrong:
java.lang.ExceptionInInitializerError (no error message)
> Unknown hardware platform: riscv64
s390x:
FAILURE: Build failed with an exception.
* What went wrong:
java.lang.ExceptionInInitializerError (no error message)
> Unknown hardware platform: s390x
Not a tremendous amount of help, though it's curious we're looking for a hardware platform. If I add some options to the execution on my riscv64 board, it looks like Kotlin native is doing things - which is strange.
FAILURE: Build failed with an exception.
* What went wrong:
Could not initialize class org.jetbrains.kotlin.gradle.utils.NativeCompilerDownloader
> Exception org.jetbrains.kotlin.konan.target.TargetSupportException: Unknown hardware platform: riscv64 [in thread "Daemon worker"]
It looks like d85357393d3fdabb5f7866f845e508faa2c009a5 is responsible for this regression.
Specifically the Kotlin bump from 2.0.20 to 2.1.20. Some testing on riscv64 seems to indicate this broke with 2.1.20 specifically, 2.1.10 seems to be fine. I will have to take a deeper look (and/or open a ticket with Kotlin) to get newer versions back on track
In the short term, I will push a change to downgrade the Kotlin version to 2.1.10 and hopefully that'll fix it across all broken platforms. If you can carry that commit as a patch it should fix this on v1.6.5 and hopefully by the next release this is just working, one way or another.
Thanks a lot! I did: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/84806
I am seeing this with extremely minimal test cases. I've reported this to JetBrains as KT-77977.
JetBrains has fixed this issue in Kotlin release 2.2.20-Beta1. I've confirmed their fix on riscv64. There's no set release date for 2.2.20 but then we're not really in a hurry either. We should be set for the future.
Confirmed this is working on riscv64 on the newer Kotlin releases. Jetbrains' fix should cover the other archs as well. Thanks for pointing this out, I probably never would've noticed.