Test Results

   486 files  +1     486 suites  +1   9m 5s ⏱️ +32s
 4 156 tests ±0   4 148 ✅ +1   8 💤 ±0  0 ❌  - 1 
16 378 runs  ±0  16 286 ✅ +1  92 💤 ±0  0 ❌  - 1 

Results for commit 37eb397. ± Comparison against base commit 3731e2c.

♻️ This comment has been updated with latest results.

This is another part of fixing #1443. But I am not sure how to verify this until now, please tell me if any issues.

It seems the error from CI was the same with other architecture.

Good news is that this can be built wit mvn clean verify -DskipTests=true on riscv64 machines

Other than the p2.inf changes the rest looks good. We can't get these parts in as they will break building repos by trying to put linux.riscv64 fragments in the repository but they will not be built. This should be totally irrelevant for builds that aim at riscv64.

Thanks for reviewing this. I over-referenced to add support eclipse from other architectures.

Looks good now.

Thanks for approving this.:)

Now I am still get the FAILURE on riscv64 hardware, this is log. Could you give me some advice on the next steps which how to push the porting works. TIA.

Looks good now.

Thanks for approving this.:)

Now I am still get the FAILURE on riscv64 hardware, this is log. Could you give me some advice on the next steps which how to push the porting works. TIA.

This log makes me believe that jna https://github.com/java-native-access/jna lacks freebsd.riscv64 support. If you look in https://repo1.maven.org/maven2/net/java/dev/jna/jna/5.14.0/jna-5.14.0.jar:META-INF/MANIFEST.MF you'll notice there is only com/sun/jna/freebsd-x8
6/libjnidispatch.so; processor=x86;osname=freebsd, com/sun/jna/freebs
d-x86-64/libjnidispatch.so; processor=x86-64;osname=freebsd .
You'll have to work with them to add support. You can use java-native-access/jna#1578 as an example where freebsd aarch64 was added.

This log makes me believe that jna https://github.com/java-native-access/jna lacks freebsd.riscv64 support. If you look in https://repo1.maven.org/maven2/net/java/dev/jna/jna/5.14.0/jna-5.14.0.jar:META-INF/MANIFEST.MF you'll notice there is only com/sun/jna/freebsd-x8 6/libjnidispatch.so; processor=x86;osname=freebsd, com/sun/jna/freebs d-x86-64/libjnidispatch.so; processor=x86-64;osname=freebsd . You'll have to work with them to add support. You can use java-native-access/jna#1578 as an example where freebsd aarch64 was added.

Thanks, I will look at this.

This log makes me believe that jna https://github.com/java-native-access/jna lacks freebsd.riscv64 support. If you look in https://repo1.maven.org/maven2/net/java/dev/jna/jna/5.14.0/jna-5.14.0.jar:META-INF/MANIFEST.MF you'll notice there is only com/sun/jna/freebsd-x8 6/libjnidispatch.so; processor=x86;osname=freebsd, com/sun/jna/freebs d-x86-64/libjnidispatch.so; processor=x86-64;osname=freebsd . You'll have to work with them to add support. You can use java-native-access/jna#1578 as an example where freebsd aarch64 was added.

Thanks for the pointer again.

The issue has been confirmed from jna upstream also, see the PR.

But a harder problem for me now is how can I replace this jna with the modified locally.

There is the com.sun.jna with version defined. So can I comment out the line and put the jna updated into /$HOME/.m2/repository. From the original build stack log, can I assume this jar is stored in /$HOME/.m2/repository/p2/osgi/bundle/com.sun.jna/5.14.0.v20231211-1200/ (or other place)?

Can this way work?

TIA.

@yuzibo I would go for local mvn install of fixed jna version (preferably with bumped version) and require that version in the target file otherwise you risk maven overriding after/when it sees checksums mismatch (I am not 100% sure here).