linux/meta-java.git, branch mickledore

Add compatability with GCC 12.x

2024-02-04T00:38:27+00:00

Fixes build for kas 4.2 and Yocto Project 4.3.2 Signed-off-by: Evgeny Sagatov Backport from 8c0c9f13cb89008f080fded0ca435f388e97bd7b Signed-off-by: Tim Orling

xerces-j: update SRC_URI

2023-06-10T07:04:58+00:00

The archive URL has changed slightly, add missing /source/. https://archive.apache.org/dist/xerces/j/source/ Signed-off-by: Tim Orling

Remove checksum

2023-05-23T11:22:16+00:00

Switch to use git SRCREV

2023-05-23T11:22:16+00:00

Update rhino download link

2023-05-23T11:22:16+00:00

openjdk-8: Update patches for patch fuzz for Yocto 4.2 mickledore

2023-05-02T07:02:27+00:00

Yocto 4.2 bitbake is more pedantic on patch fuzz, which treats patch fuzz Warnings as Errors, and fails the bulid. Corrected patch fuzz with: devtool modify openjdk-8-native devtool finish --force-patch-refresh openjdk-8-native but removed the changes to 1001-hotspot-fix-crash-on-JNI_CreateJavaVM.patch which rewrote a huge amount of source files in their entirety for some reason. Signed-off-by: Geoff Parker

Merge pull request #3 from kk6ho/master+mickledore

2023-03-16T07:54:16+00:00

layer.conf: Switch LAYERSERIES_COMPAT to mickledore

2023-01-16T20:17:44+00:00

Signed-off-by: Geoff Parker

conf: layer: add free(1) to HOSTTOOLS_NONFATAL for icedtea7-native

2022-12-12T05:58:40+00:00

icedtea7-native build uses free -m (from the procfs suite of tools) to determine memory bound during compile. This always fails for us, because free is not passed through from the host environment. This results in a few warnings in the logs: /bin/sh: line 1: free: command not found [..snip..]/Sanity-Settings.gmk:195: WARNING: MB_OF_MEMORY should not be empty [Sanity-Settings.gmk] But otherwise this is handled gracefully. Problems arise when building icedtea7-native on hosts with more modest RAM sizes: Build process will consume so much RAM that the OOM killer is invoked. Let us avoid this by passing through free from the host environment. We use HOSTTOOLS_NONFATAL instead of HOSTTOOLS as to not break currently working setups that have enough RAM but lack free(1). This needs to be done globally due to the way HOSTTOOLS_NONFATAL is evaluated, we thus stick it into the layer.conf. Signed-off-by: Ahmad Fatoum Signed-off-by: Richard Leitner

jsch: switch to inclusive language

2022-11-28T19:59:12+00:00

Signed-off-by: Ulrich Ölmann Signed-off-by: Richard Leitner