NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
4d203fedfb
kumquat-buildroot/package/openjdk-bin/openjdk-bin.hash

10 lines
609 B
Plaintext
Raw Normal View History

package/openjdk{, -bin}: bump latest to version 16.0.1+9 When introducing OpenJDK to buildroot, the OpenJDK project did not put releases on their GitHub page. Since then, the OpenJDK developers have not only added OpenJDK releases to Github, they are starting to phase out adding releases to their public-facing mercurial repository. Compare the following URLs: https://wiki.openjdk.java.net/display/JDKUpdates/JDK+14u https://wiki.openjdk.java.net/display/JDKUpdates/JDK+15u https://wiki.openjdk.java.net/display/JDKUpdates/JDK+16u With JDK14, only the mercurial repository is listed. With OpenJDK15, both the GitHub and mercurial repository are listed. Finally, with OpenJDK16, only the GitHub repository is listed. For consistency's sake, and for the version bump of JDK latest from 14 to 16 do the following: - Change the repository for OpenJDK14 to point to the official GitHub repository, - In order to simplify and reuse the GitHub URL, modify the OPENJDK_VERSION_MAJOR and OPENJDK_VERSION_MINOR definitions to only include a single number for the MAJOR definition. - Change openjdk-bin.mk to also use the same format as the openjdk.mk file Unfortunately, we can't yet do the switch for OpenJDK11: the Github repository is missing a Mercurial-related file, so that the archive for OpenJDK11 11.0.11+9 would change from the one we already have on s.b.o and that people would alreay have locally, and we'd have a hash mismatch, either on master, or on all pur previous relases. OpenJDK11 just got a new release mere hours ago (as of this writing), but it hasn't yet trickled down to AdoptOpenJDK/openjdk11-binaries, so we can't do the bump just yet... Add a note to the OpenJDK11 case, to prepare the migration to Github with the next version bump. Finally, remove upstreamed patch 0001-fix-gcc-10-support.patch as it's no longer needed. Signed-off-by: Adam Duskett <aduskett@gmail.com> [yann.morin.1998@free.fr: - meld the github switch and 14->16 bump together - drop the github switch for 11 9because hash mismatch) - expand commit log accordingly ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-05-04 23:00:25 +02:00
# From https://github.com/AdoptOpenJDK/openjdk16-binaries/releases
package/openjdk{-bin}: bump versions to 11.0.12+7 and 16.0.2+7 As the github repository has changed from github.com/AdoptOpenJDK/ to github.com/adoptium, both versions are updated in the same patch. Signed-off-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-09-18 02:50:27 +02:00
sha256 323d6d7474a359a28eff7ddd0df8e65bd61554a8ed12ef42fd9365349e573c2c OpenJDK16U-jdk_x64_linux_hotspot_16.0.2_7.tar.gz
package/openjdk-bin: new package Paradoxically, building OpenJDK requires a pre-existing JDK. This pre-existing JDK is called the "boot JDK." The boot JDK for building JDK major version N should be a JDK of major version N-1, so for building JDK11, JDK10 would be needed. This requirement is an issue when building on most distributions, as the host JDK tends to be JDK8. The AdoptOpenJDK project provides binaries that can act as the boot JDK to build the target JDK, which is what this package provides. Currently, only a x86_64 host is supported, for two reasons: 1) A 32bit x86 binary distribution is not available from AdoptOpenJDK 2) We didn't had access to a host machine using an architecture other than x86-64 The provided unpack200 has an invalid RPATH and relies on libzlib. When host-libzlib runs the install step, the following error is generated: *** ERROR: package host-libzlib installs executables without proper RPATH: *** $(HOST_DIR)/bin/unpack200 Because unpack200 is a deprecated tool, removing it after installation is safe and fixes the issue. Signed-off-by: Adam Duskett <Aduskett@gmail.com> [Thomas: - fix comments in the code - use the more usual "cp -dpfr" command to copy files over] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-02-05 15:31:24 +01:00
package/openjdk{-bin}: bump versions to 11.0.12+7 and 16.0.2+7 As the github repository has changed from github.com/AdoptOpenJDK/ to github.com/adoptium, both versions are updated in the same patch. Signed-off-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-09-18 02:50:27 +02:00
# From https://github.com/adoptium/temurin11-binaries/releases
sha256 8770f600fc3b89bf331213c7aa21f8eedd9ca5d96036d1cd48cb2748a3dbefd2 OpenJDK11U-jdk_x64_linux_hotspot_11.0.12_7.tar.gz
package/{openjdk, openjdk-bin}: add support for building either lts or latest As Java is used quite a bit in the enterprise world, having the option to build the LTS version of OpenJDK is quite convenient and also a requirement for many companies wanting to use Java. As such, there are three options: 1) Continue only to support the latest version of OpenJDK. 2) Downgrade our existing OpenJDK package from 14 to 11. 3) Add an option to support either OpenJDK 11 or 14. OpenJDK 11 and 14 currently have: - The same configure options. - The same license files and hashes for those license files. - The same dependencies. - The same method to build and install. As such, supporting both 11 and 14 is not only an easy option to add to Buildroot, but also a nice feature for users who wish to use Java in an embedded environment with a company that mandates the use of the LTS version. To make it explicit that this choice really is about LTS vs. latest, and not about 11 vs. 14, the options are really named with LTS and LATEST, so that future defconfigs will not have to migrate when the versions changes (e.g. we update from 14->15, or from 11 to the next LTS). Signed-off-by: Adam Duskett <Aduskett@gmail.com> [yann.morin.1998@free.fr: - keep latest as the default, for existing defconfigs - rename options: drop numbers, use LTS and LATEST ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-04-22 21:21:18 +02:00
package/openjdk-bin: new package Paradoxically, building OpenJDK requires a pre-existing JDK. This pre-existing JDK is called the "boot JDK." The boot JDK for building JDK major version N should be a JDK of major version N-1, so for building JDK11, JDK10 would be needed. This requirement is an issue when building on most distributions, as the host JDK tends to be JDK8. The AdoptOpenJDK project provides binaries that can act as the boot JDK to build the target JDK, which is what this package provides. Currently, only a x86_64 host is supported, for two reasons: 1) A 32bit x86 binary distribution is not available from AdoptOpenJDK 2) We didn't had access to a host machine using an architecture other than x86-64 The provided unpack200 has an invalid RPATH and relies on libzlib. When host-libzlib runs the install step, the following error is generated: *** ERROR: package host-libzlib installs executables without proper RPATH: *** $(HOST_DIR)/bin/unpack200 Because unpack200 is a deprecated tool, removing it after installation is safe and fixes the issue. Signed-off-by: Adam Duskett <Aduskett@gmail.com> [Thomas: - fix comments in the code - use the more usual "cp -dpfr" command to copy files over] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-02-05 15:31:24 +01:00
# Locally calculated
package/{openjdk, openjdk-bin}: bump version to 14.0.1+7 Signed-off-by: Adam Duskett <Aduskett@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-04-22 21:21:17 +02:00
sha256 4b9abebc4338048a7c2dc184e9f800deb349366bdf28eb23c2677a77b4c87726 legal/java.prefs/LICENSE
sha256 a44eb7b5caf5534c6ef536b21edb40b4d6babf91bf97d9d45596868618b2c6fb legal/java.prefs/ASSEMBLY_EXCEPTION
Reference in New Issue Copy Permalink