I'm searching if it's possible to build twice the same Linux Kernel (same sources, same environment, same options, same compiler) and get the the same checksum. Anybody knows how to do?
views:
243answers:
5
+1
A:
Quickest way to check would be to make, take a copy, make clean, and then make again. If the checksum matches, then its possible. If not then that suggests that Make is altering some source files in some way (build numbering, build date etc)
Visage
2009-06-29 08:06:25
+1
A:
Presumably, building the kernel in the same environment will result in the same checksum. So, same compiler (same version of the same compiler), exactly the same source, same dependencies (if that's even applicable to a kernel compile), etc.
Kevin Montrose
2009-06-29 08:06:35
Even with exactly the same environment setup (same sources, same compiler and same dependencies) two successive build give a different checksum. I think the problem is around compilation options and I don't know which compilation options it's possible to change to get the same checksum without modify the kernel correctness.
2009-06-29 08:45:46
+3
A:
The date of build is included in the version, see init version.c :
const char linux_banner[] =
"Linux version " UTS_RELEASE " (" LINUX_COMPILE_BY "@"
LINUX_COMPILE_HOST ") (" LINUX_COMPILER ") " UTS_VERSION "\n";
and UTS_VERSION is defined in include/linux/compile.h :
/* This file is auto generated, version 1 */
/* PREEMPT */
#define UTS_MACHINE "arm"
#define UTS_VERSION "#1 PREEMPT Mon Jun 29 10:49:17 CEST 2009"
#define LINUX_COMPILE_TIME "10:49:17"
#define LINUX_COMPILE_BY "cynove"
#define LINUX_COMPILE_HOST "jp"
#define LINUX_COMPILE_DOMAIN "evonyc"
#define LINUX_COMPILER "gcc version 4.3.2 (crosstool-NG-1.4.0) "
compile.h is generated by scripts/mkcompile_h, where you find the following line :
UTS_VERSION="$UTS_VERSION $CONFIG_FLAGS `LC_ALL=C LANG=C date`"
By removing the date from the pervious line, you should be able to get rid of the build time dependency.
shodanex
2009-06-29 09:08:28
A:
Even a simple hello world compiled twice results in different binaries. Somehow the linker is adding some information that changes in each build.
felipec
2009-06-29 09:10:20
A:
shodanex's answer is right but incomplete. After some research I found Linux kernel binary embeds a default ramfs which is another reason of differences between two kernels compilations (CPIO RAMFS header embeds date). It's impossible to disable this feature but it's possible to provide a default ramfs. When you do so, you get exactly the same checksum.
Thank you. Your answers help me a lot to resolve my problem.