Should we use GCC11 for building Alpine JDK19+? #3001
Labels
aarch
Issues that affect or relate to the aarch ARCHITECTURE
alpine-linux
Issues that affect or relate to the Alpine LINUX OS
docker
Issues related to our docker files and docker scripts
enhancement
Issues that enhance the code or documentation of the repo in any way
question
Issues that are queries about the code base or potential problems that have been spotted
#2990 highlighted an issue where an upgrade to the docker base image from 3.15 to 3.16 bumped the GCC version from 10 to 11. This was fixed by locking the version of the build container to 3.15 so it continued to use the GCC10 compiler built into that Alpine version.
On (non-Alpine) Linux/x64 we use different compiler versions based on the java versions. Should we do the same for Alpine? Since we've already shipped versions of all JDKs up to 17 on GCC10 I'm ok with leaving them as-is, but we have recently bumped Linux platforms up to GCC11, and we could do the same for Alpine.
I've got a built version of GCC11.2 for Alpine/x64 at https://ci.adoptopenjdk.net/userContent/gcc/gcc112.alpinex64.tar.xz and it appears to work ok for building JDK head on Alpine 3.15 (Built with
--disable-libsanitizer
) NOTE: I haven't got a working one for Alpine/aarch64 yet.This issue should cover whether we want to do it and any subsequent PRs to this repository and infrastructure covering any required PRs.
The text was updated successfully, but these errors were encountered: