summaryrefslogtreecommitdiffstats
path: root/recipes-core/jamvm/jamvm
Commit message (Collapse)AuthorAgeFilesLines
* jamvm: refresh patchesMaxin B. John2018-04-093-21/+47
| | | | | | | | | | | | | | | | | | | | | | 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>
* jamvm: update git version to ebd11bde0a97b57f0d18938c6b65468d3c932719Henning Heinold2014-04-161-31/+0
| | | | * remove annotations.patch, because it was fixed upstream
* jamvm: update to git revision ac22c9948434e528ece451642b4ebde40953ee7eHenning Heinold2013-09-291-0/+31
| | | | * fix gnuclasspath annotations
* jamvm: work around min heap size greater than max errorJan Luebbe2012-05-251-0/+15
| | | | | | | | | | 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>
* meta-java: initial commitHenning Heinold2011-11-262-0/+82
* taken over mostly stuff from oe classic * cleaned up recipes * added license checksums * bump icedtea6-native to 1.8.11 * use jamvm from git as native