Kernel-testers Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
* Building vmlinux without date/timestamp bits
@ 2009-06-12 22:15 John Daiker
       [not found] ` <4A32D37E.40507-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
  0 siblings, 1 reply; 2+ messages in thread
From: John Daiker @ 2009-06-12 22:15 UTC (permalink / raw)
  To: kernel-janitors-u79uwXL29TY76Z2rM5mHXA
  Cc: kernel-testers-u79uwXL29TY76Z2rM5mHXA

I'm working on various trivial patches (mainly whitespace and 
checkpatch.pl cleanups).

I read quite some time ago that it's best to md5sum the vmlinux file 
before and after these trivial patches are applied (to ensure that no 
executable code has changed, modules on a binary level are identical, etc).

So far, I have no problems producing identical .o and .ko files with my 
trivial patches.  My problem lies in the resulting vmlinux and vmlinux.o 
file, though.

I know the files are different due to date/timestamping the kernel, but 
I'm not sure where this happens (and how I can prevent it).  Are there 
pieces of code and/or Makefile that I can comment out so that the 
resulting vmlinux file isn't timestamped (and thus would be an exactly 
identical before and after).  I know it can be done... I've done it 
before (years ago), but seem to have forgotten the trick.

Thanks for the help!

John Daiker

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-06-12 23:43 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-12 22:15 Building vmlinux without date/timestamp bits John Daiker
     [not found] ` <4A32D37E.40507-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-06-12 23:43   ` Peter Huewe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox