From: Jouni Hogander <jouni.hogander@xxxxxxxxxx> Initramfs configuration has impact on build being reproducible Signed-off-by: Jouni Hogander <jouni.hogander@xxxxxxxxxx> --- Documentation/kbuild/reproducible-builds.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Documentation/kbuild/reproducible-builds.rst b/Documentation/kbuild/reproducible-builds.rst index 3b25655e441b..559700531a48 100644 --- a/Documentation/kbuild/reproducible-builds.rst +++ b/Documentation/kbuild/reproducible-builds.rst @@ -119,6 +119,14 @@ To avoid this, you can make the vDSO different for different kernel versions by including an arbitrary string of "salt" in it. This is specified by the Kconfig symbol ``CONFIG_BUILD_SALT``. +Initial RAM Filesystem +---------------------- + +If ``CONFIG_BLK_DEV_INITRD`` is enabled and ``CONFIG_INITRAMFS_SOURCE`` +doesn't contain gzipped cpio archive, an initramfs is generated during +build. To avoid this provide gzipped cpio archive via +``CONFIG_INITRAMFS_SOURCE`` + .. _KBUILD_BUILD_TIMESTAMP: kbuild.html#kbuild-build-timestamp .. _KBUILD_BUILD_USER and KBUILD_BUILD_HOST: kbuild.html#kbuild-build-user-kbuild-build-host .. _KCFLAGS: kbuild.html#kcflags -- 2.17.1
