From: "Edgardo Hames" <ehames@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: "Sam Ravnborg" <sam@ravnborg.org>
Subject: Re: Rebuilding and checksumming the Linux kernel
Date: Sun, 1 Apr 2007 18:53:18 -0300 [thread overview]
Message-ID: <478c16ae0704011453j7942bb3aq15c9930045db9e50@mail.gmail.com> (raw)
In-Reply-To: <20070401210622.GC10761@uranus.ravnborg.org>
On 4/1/07, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Sun, Apr 01, 2007 at 03:56:30PM -0300, Edgardo Hames wrote:
> > I'm working on a project with teams spread across the world and we all
> > work on the same repository patching the kernel and then integrating
> > into a common main branch. Even though we label the source code, we
> > would like to make sure that we are all building the same kernel by
> > running md5sum on the resulting binary.
> >
> > Right now, this is not possible because the kernel includes a
> > timestamp and a build number on the binary. What are this timestamps
> > used for? Can we just remove them? Is there any other thing that may
> > lead to different binaries? (we are using the exact toolchains and
> > build machines, so we can assume that the same executable is generated
> > if the input source is the same).
>
> Soon you will be able to say:
>
> KBUILD_BUILD_TIMESTAMP="2007-02-30 01:02.03" KBUILD_BUILD_VERSION=99 make
>
> It will hit -mm soon and mainline in next merge window.
> Patch is in kbuild.git at git.kernel.org.
This is so much more than I could have asked for! I will try this
patch on my version of the kernel.
Thanks a lot,
Ed
--
Encontrá a "Tu psicópata favorito" http://tuxmaniac.blogspot.com
The future is not what it used to be.
-- Paul Valéry
next prev parent reply other threads:[~2007-04-01 21:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 18:56 Edgardo Hames
2007-04-01 18:58 ` Arjan van de Ven
2007-04-01 19:02 ` Jan Engelhardt
2007-04-01 21:02 ` David Schwartz
2007-04-01 21:06 ` Sam Ravnborg
2007-04-01 21:53 ` Edgardo Hames [this message]
2007-04-02 1:03 ` Edgardo Hames
2007-04-02 1:41 ` Jan Engelhardt
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=478c16ae0704011453j7942bb3aq15c9930045db9e50@mail.gmail.com \
--to=ehames@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®