aboutsummaryrefslogtreecommitdiffstats
path: root/recipes-core/jamvm/jamvm/jamvm-minmax-heap.patch
AgeCommit message (Collapse)Author
2018-04-09jamvm: refresh patchesMaxin B. John
Fixes this: Some of the context lines in patches were ignored. This can lead to incorrectly applied patches. The context lines in the patches can be updated with devtool: devtool modify <recipe> devtool finish --force-patch-refresh <recipe> <layer_path> Then the updated patches and the source tree (in devtool's workspace) should be reviewed to make sure the patches apply in the correct place and don't introduce duplicate lines (which can, and does happen when some of the context is ignored). Further information: http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450 Details: patching file src/Makefile.am Hunk #1 succeeded at 23 with fuzz 1. Signed-off-by: Maxin B. John <maxin.john@intel.com>
2012-05-25jamvm: work around min heap size greater than max errorJan Luebbe
On system with large amounts of RAM (such as 96GB), the default initial heap size is larger than the max heap size specified in some build commands. Set min_heap to the max_heap value in those cases instead. Signed-off-by: Jan Luebbe <jlu@pengutronix.de> Signed-off-by: Henning Heinold <heinold@inf.fu-berlin.de>