mirror of
https://git.yoctoproject.org/poky
synced 2026-05-31 12:49:46 +00:00
kernel.bbclass: Include randstruct seed assets in STAGING_KERNEL_BUILDDIR
When building with CONFIG_MODVERSIONS=y and CONFIG_RANDSTRUCT=y we need to copy the build assets generated for the randstrutc seed to STAGING_KERNEL_BUILDDIR, otherwise the out-of-tree modules build will generate those assets which will result in a different RANDSTRUCT_HASHED_SEED. (From OE-Core rev: d6cb9dce1ffb14f9db497e9bb0cb7265ea4064ec) Signed-off-by: Diego Sueiro <diego.sueiro@arm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> (cherry picked from commit b36303158b2e0273ff415bdedefb379f680b30fc) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
d146636e7f
commit
2836daa4c8
@@ -585,6 +585,22 @@ do_shared_workdir () {
|
|||||||
cp tools/objtool/objtool ${kerneldir}/tools/objtool/
|
cp tools/objtool/objtool ${kerneldir}/tools/objtool/
|
||||||
fi
|
fi
|
||||||
fi
|
fi
|
||||||
|
|
||||||
|
# When building with CONFIG_MODVERSIONS=y and CONFIG_RANDSTRUCT=y we need
|
||||||
|
# to copy the build assets generated for the randstruct seed to
|
||||||
|
# STAGING_KERNEL_BUILDDIR, otherwise the out-of-tree modules build will
|
||||||
|
# generate those assets which will result in a different
|
||||||
|
# RANDSTRUCT_HASHED_SEED
|
||||||
|
if [ -d scripts/basic ]; then
|
||||||
|
mkdir -p ${kerneldir}/scripts
|
||||||
|
cp -r scripts/basic ${kerneldir}/scripts
|
||||||
|
fi
|
||||||
|
|
||||||
|
if [ -d scripts/gcc-plugins ]; then
|
||||||
|
mkdir -p ${kerneldir}/scripts
|
||||||
|
cp -r scripts/gcc-plugins ${kerneldir}/scripts
|
||||||
|
fi
|
||||||
|
|
||||||
}
|
}
|
||||||
|
|
||||||
# We don't need to stage anything, not the modules/firmware since those would clash with linux-firmware
|
# We don't need to stage anything, not the modules/firmware since those would clash with linux-firmware
|
||||||
|
|||||||
Reference in New Issue
Block a user