Kernel-testers Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Daiker <daikerjohn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: kernel-janitors-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Building vmlinux without date/timestamp bits
Date: Fri, 12 Jun 2009 15:15:26 -0700	[thread overview]
Message-ID: <4A32D37E.40507@gmail.com> (raw)

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

             reply	other threads:[~2009-06-12 22:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 22:15 John Daiker [this message]
     [not found] ` <4A32D37E.40507-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-06-12 23:43   ` Building vmlinux without date/timestamp bits Peter Huewe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A32D37E.40507@gmail.com \
    --to=daikerjohn-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=kernel-janitors-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox