summaryrefslogtreecommitdiffstats
path: root/recipes-core/openjdk/patches-openjdk-8/0008-autoconf-fix-shark-build-common.patch
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2022-10-28 18:16:34 +0200
committerRichard Leitner <richard.leitner@skidata.com>2022-12-12 06:58:40 +0100
commit79df369e89ed72ebdfe84a4a520ed590751ae5d9 (patch)
tree0090dcff65eacde766112dd0c653f80ac35bc41f /recipes-core/openjdk/patches-openjdk-8/0008-autoconf-fix-shark-build-common.patch
parentfc4f7444dc4bd261c2dd4eca3e186f6be3eca3fc (diff)
downloadmeta-java-79df369e89ed72ebdfe84a4a520ed590751ae5d9.tar.gz
conf: layer: add free(1) to HOSTTOOLS_NONFATAL for icedtea7-native
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 <a.fatoum@pengutronix.de> Signed-off-by: Richard Leitner <richard.leitner@skidata.com>
Diffstat (limited to 'recipes-core/openjdk/patches-openjdk-8/0008-autoconf-fix-shark-build-common.patch')
0 files changed, 0 insertions, 0 deletions