On Wed, 30 Apr 2025 19:41:52 GMT, Vladimir Ivanov <vliva...@openjdk.org> wrote:
> Overall, it still looks like a JDK build issue to me. Hiding problems > occurred during the build is not good. If some toolchains can't successfully > build the library, the library shouldn't be included in JDK. No, in riscv case (possiblely also on arm?) I don't think it's a build issue, the jdk vendor can choose to support it or not, it's just the way passing the information ( whether it's supported or not) are different. How about we consider this in another way, we could fix this issue first, as it fails regularly on riscv and x64 in some situations. Then if you still consider the existing behaviour should be changed and could be improved further, it can be done in another pr. After all, it already broke the existing jdk in some scenarios. How do you think about it? ------------- PR Comment: https://git.openjdk.org/jdk/pull/24914#issuecomment-2844401476
