From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 01/22] Remove the DATE variable
Date: Tue, 24 Apr 2012 10:31:15 +0200 [thread overview]
Message-ID: <87bomhh6p8.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CAAXf6LVp-d330GhUgrz_fXcj=k5mYK2K-RyxqLw+7sVRqw4L=g@mail.gmail.com> (Thomas De Schampheleire's message of "Tue, 24 Apr 2012 09:43:10 +0200")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> writes:
Hi,
Thomas> A disadvantage of adding changing variables like DATE is that
Thomas> two builds that are built from the exact same set of sources,
Thomas> are not binary equal. You cannot simply compare the rootfs
Thomas> image and expect no differences. You'd have to unpack the
Thomas> rootfs and compare file by file, leaving out files like
Thomas> /etc/os-release that would contain a date.
Thomas> I haven't yet looked at which binaries inside a typical rootfs do
Thomas> contain such changing variables, but I will do that for my
Thomas> configuration in the near future. My intention is to ensure binary
Thomas> equality for the entire rootfs.
I think you'll find that this is quite common. From the top of my head I
know that atleast the Linux kernel and busybox adds the build time to
the binary, so I doubt this will really work.
Thomas> With this in mind, I would not favor adding a DATE of some kind
Thomas> to a file in buildroot just to mark a variable as used, unless
Thomas> we provide a way to override DATE in the config file (in the
Thomas> Linux kernel, the 'user' and 'machine' etc. build variables are
Thomas> also overridable.
You can always build with make DATE=foo
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-04-24 8:31 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 14:45 [Buildroot] [pull request] Pull request for branch for-2012.05/misc-cleanups Thomas Petazzoni
2012-04-17 14:45 ` [Buildroot] [PATCH 01/22] Remove the DATE variable Thomas Petazzoni
2012-04-21 13:05 ` Arnout Vandecappelle
2012-04-22 8:23 ` Peter Korsgaard
2012-04-22 15:32 ` Thomas Petazzoni
2012-04-22 19:55 ` Peter Korsgaard
2012-04-24 7:43 ` Thomas De Schampheleire
2012-04-24 8:31 ` Peter Korsgaard [this message]
2012-04-17 14:45 ` [Buildroot] [PATCH 02/22] Remove cc-option: not used anywhere Thomas Petazzoni
2012-04-19 13:54 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 03/22] Remove filename extension crap for OS compatibility Thomas Petazzoni
2012-04-19 14:03 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 04/22] kconfig: do not use HOST_LOADLIBES anymore Thomas Petazzoni
2012-04-19 14:05 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 05/22] Rename Makefile.autotools.in to pkg-autotargets.mk Thomas Petazzoni
2012-04-19 14:08 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 06/22] Rename Makefile.cmake.in to pkg-cmaketargets.mk Thomas Petazzoni
2012-04-19 14:06 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 07/22] Split Makefile.package.in in pkg-download.mk, pkg-utils.mk and pkg-gentargets.mk Thomas Petazzoni
2012-04-19 14:07 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 08/22] pkg-*.mk: add some comments, update some existing comments Thomas Petazzoni
2012-04-19 14:08 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 09/22] Remove unused .fakeroot.* mechanism Thomas Petazzoni
2012-04-19 14:09 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 10/22] Move the manual build infrastructure to docs/manual/manual.mk Thomas Petazzoni
2012-04-19 22:01 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 11/22] cmake: move creation of toolchain file to package/pkg-cmaketargets.mk Thomas Petazzoni
2012-04-19 22:01 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 12/22] package: remove unused STRIP_DISCARD_ALL variable Thomas Petazzoni
2012-04-24 22:03 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 13/22] Remove unused GNU_TARGET_SUFFIX Thomas Petazzoni
2012-04-25 6:55 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 14/22] toolchain: remove useless indirect variables Thomas Petazzoni
2012-04-25 6:56 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 15/22] gcc: remove unused EXTRA_GCC2_CONFIG_OPTIONS Thomas Petazzoni
2012-04-25 6:58 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 16/22] gcc: remove unused EXTRA_GCC4_CONFIG_OPTIONS Thomas Petazzoni
2012-04-25 6:59 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 17/22] gcc: remove unused ARCH_FPU_SUFFIX Thomas Petazzoni
2012-04-25 7:00 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 18/22] gcc: move version/snap variables to gcc-uclibc-4.x.mk Thomas Petazzoni
2012-04-25 7:01 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 19/22] toolchain: remove toolchain/Makefile.in and toolchain/gcc/Makefile.in Thomas Petazzoni
2012-04-25 7:47 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 20/22] gcc: remove unused EXTRA_GCC1_CONFIG_OPTIONS Thomas Petazzoni
2012-04-25 7:47 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 21/22] mklibs: remove support Thomas Petazzoni
2012-04-25 7:56 ` Peter Korsgaard
2012-04-17 14:45 ` [Buildroot] [PATCH 22/22] xtensa: remove support for this architecture Thomas Petazzoni
2012-04-25 8:44 ` Peter Korsgaard
2012-04-25 9:09 ` Thomas Petazzoni
2012-04-25 9:21 ` Peter Korsgaard
2012-04-25 11:02 ` Thomas Petazzoni
2012-04-26 4:55 ` Marc Gauthier
2012-04-26 6:07 ` Peter Korsgaard
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=87bomhh6p8.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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