The Adoptium team stopped supporting arm32 hardware with Java 21, but many still rely on arm32 devices (like older Raspberry Pis) and OS.
(https://adoptium.net/de/supported-platforms/)
thank you very much for providing the JRE/JDK. This is a great time saver and helps us a lot! We have now been able to roll out your Java 21 package on many systems without any problems.
Unfortunately we have a few old systems running a raspberry buster distribution and we don’t want to do a distribution update to raspberry bullseye remotely. Buster uses GLIBC 2.28. Whereas your packages of JRE/JDK21 are compiled with GLIBC Support for > 2.29.
Easiest way seems to be, to build JRE/JDK21 for a system with GLIBC2.28 support. As far as I see it, Adoptium provides docker container for building
Our naive approach would it be, to create a new version based on the cross toolchain for Java 17 for arm and simply replace the Java 17 with the Java 21 source code.
Do you think this is possible and it is a good starting point?
I remember, that it it once took me several weeks of time to cross compile some bigger programs. How much time did you spend to build the debian packages? Do you remember any show stopper on building java 21 with glibc 2.28. Of course you can’t probably do an estimation on this. I am more interested in your gut feeling on this. I ask, because we are talking about ~10 old Systems. It may be more economic to simply exchange the old systems.
Great efforts, thank you. I allowed to borrow your JVM package for openHABian, the OS companion to openHAB. We just moved openHAB to Java 21 and just like yourself now have trouble supporting older Raspberries that don’t have enough RAM to run in 64 bit. Hope that’s okay for you?
So far everything seems to be working just as fine as with regular 64bit Temurin 21.
Do you have any plans to update the packages? I think we’re on .8 meanwhile.
No I don’t use OpenEMS. As I wrote I use the JVM 21 package in openHABian. openHAB and its OS are well known OSS projects you will have come across I guess.
we have OpenEMS running locally, but for deployment in the field we also need a arm32 bit version.
we are building it into a docker image for ease of deployment, but run into an issue with the security policies:
SecurityException: Couldn’t iterate through the jurisdiction policy files: unlimited
Anyone had issues with that? Certificates/policies?
Thats a bit of chicken/egg thing I did get into contact already, i have the docs here for signing up. But if we cant get it to run, it’s not really a solid replacement for our own EMS. We have more than 300 units in the field on arm32.
We are working hard to solve our current setup within OpenEMS. If we succeed we will defnitely join.
we have managed to get it all running.
it was indeed an emulation error with a docker file for armv7 on windows. Apparently the emulation is not 100%. It runs fine on actual hardware.
we use bellsoft arm32 release now on our devices and all is going smoothly now. Also UI is ported it seems.
Dear @da-Kai … Do you know whether there is an OpenJDK 21 for ARM32 platform out as ZIP or TGZ? Had been hard to install the Debian package on our ARM32 test system. Somebody told me there is one, but I cannot find it.