summaryrefslogtreecommitdiffstats
path: root/recipes-containers/criu/files/0001-criu-Fix-toolchain-hardcode.patch
Commit message (Collapse)AuthorAgeFilesLines
* criu: upgrade 3.11 -> 3.12Yuan Chao2019-08-121-5/+7
| | | | | | | Refresh patch: 0001-criu-Fix-toolchain-hardcode.patch Signed-off-by: Yuan Chao <yuanc.fnst@cn.fujitsu.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* criu: uprev to version 3.10Mark Asselstine2018-08-021-6/+7
| | | | | | | | | | | | | | | | | | | | | | A fairly straightforward uprev requiring minimal patch refreshing since a few hunks were failing due to conflicts with upstream updates. Unfortunately upstream starting using the now overloaded "PYTHON" variable in their Makefiles, this is not the path to the python executable but rather the name 'python2' or 'python3' which is used to determine which local directories to include. Due to this we must explicitly assign values to 'PYTHON_FULL' and 'PYTHON'. We use 'python2' since we are using 'setuptools' and therefore are explicitly using python v2, at some point we might want to make this recipe work with either python v2 or v3 but for now we continue to explicitly use v2. Instead of using version specific filename we switch to using _git.bb which is inline with similar 'git' recipes found in oe-core and other repos. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* criu: refresh patches to fix QA warningYi Zhao2018-04-131-4/+2
| | | | | | | Refresh patches with devtool command to fix do_patch warning. Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* criu: uprev to version 3.4Mark Asselstine2017-09-101-34/+23
| | | | | | | | | | | | | | | | | | | | Our current version of criu is about a year old and has some compilation issues with the latest gcc (currently it is unbuildable). Since the version of criu and the kernel version are fairly tightly coupled it wouldn't be surprising of this old criu would also be exhibiting some runtime issues with our fairly new kernel version. With the above in mind we uprev to criu v3.4 which was recently released. This requires several of the patches to be updated (mostly context). We are able to drop the selinux related change as RSS prevents the situation this was working around from happenning. This was validated using https://criu.org/Simple_loop (and a few variants). Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* criu: uprev to 2.5Jianchuan Wang2016-09-121-21/+87
| | | | | Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* criu: upgrade from version from 1.2 to 1.4Nam Ninh2015-03-301-0/+46
Upgrade criu from version from 1.2 to 1.4. criu is the only user of protobuf and only supported on x86 and arm, so limit protobuf support on x86 and arm too. Signed-off-by: Nam Ninh <nam.ninh@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>