All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: Olaf Hering <olaf@aepfle.de>,
	xen-devel@lists.xen.org,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 3/3] mini-os: sort objects in binary archives
Date: Wed, 11 Mar 2015 12:28:50 +0000	[thread overview]
Message-ID: <1426076930.21353.226.camel@citrix.com> (raw)
In-Reply-To: <20150205002246.GJ2980@type.youpi.perso.aquilenet.fr>

On Thu, 2015-02-05 at 01:22 +0100, Samuel Thibault wrote:
> Olaf Hering, le Tue 03 Feb 2015 12:45:37 +0100, a écrit :
> > When building stubdom the mini-os objects are also linked into the
> > binary. Unfortunately the linker will place them in the order found in
> > the archive. Since this order is random the resulting stubdom binary
> > differs when it was built from identical sources but on different
> > build hosts. To help with creating a reproducible binary the elements
> > in an archive must simply be sorted before passing them to $(AR).
> > 
> > Signed-off-by: Olaf Hering <olaf@aepfle.de>
> > Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> > Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>
> 
> Provided that the missing parenthesis gets fixed,
> 
> Acked-by: Samuel Thibault <samuel.thibault@ens-lyon.org>

I did s,extras/mini-os/,, on the paths and applied to mini-os.git.

I also pushed to xen.git (which includes Wei's build fix too):

commit 00f1fc5fd2bb9c7cf7f0e8a841ee741e547a4145
Author: Ian Campbell <ian.campbell@citrix.com>
Date:   Wed Mar 11 10:47:33 2015 +0000

    MINIOS_UPSTREAM_REVISION Update
    
    Signed-off-by: Ian Campbell <ian.campbell@citrix.com>

diff --git a/Config.mk b/Config.mk
index c0c0775..f457b5d 100644
--- a/Config.mk
+++ b/Config.mk
@@ -255,9 +255,9 @@ MINIOS_UPSTREAM_URL ?= git://xenbits.xen.org/mini-os.git
 endif
 OVMF_UPSTREAM_REVISION ?= a065efc7c7ce8bb3e5cb3e463099d023d4a92927
 QEMU_UPSTREAM_REVISION ?= master
-MINIOS_UPSTREAM_REVISION ?= 55f7cd7427ef3e7fe3563a3da46d8664a2ed0d6d
-# Thu Jan 29 19:10:04 2015 +0000
-# Mini-OS: standalone build
+MINIOS_UPSTREAM_REVISION ?= d0b7f0f62fd0e1154d29849b9f2e6de3783742ce
+# Tue Mar 10 13:14:38 2015 +0000
+# mini-os: replace XEN_TARGET_ARCH with MINIOS_TARGET_ARCH
 
 SEABIOS_UPSTREAM_REVISION ?= rel-1.8.0
 # Wed Feb 18 12:49:59 2015 -0500



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-03-11 12:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 11:45 [PATCH 0/3] sort various input files for reproducible build Olaf Hering
2015-02-03 11:45 ` [PATCH 1/3] docs: create reproducible html Olaf Hering
2015-02-03 11:45 ` [PATCH 2/3] etherboot: [build] sort objects in blib.a Olaf Hering
2015-02-24 16:43   ` Ian Campbell
2015-02-03 11:45 ` [PATCH 3/3] mini-os: sort objects in binary archives Olaf Hering
2015-02-03 12:28   ` Olaf Hering
2015-02-11 11:37     ` Wei Liu
2015-02-27 17:16       ` Ian Campbell
2015-02-03 13:36   ` Jan Beulich
2015-02-05  0:22   ` Samuel Thibault
2015-03-11 12:28     ` Ian Campbell [this message]
2015-02-05 12:24   ` Ian Campbell
2015-02-16 11:59     ` Olaf Hering

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=1426076930.21353.226.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=olaf@aepfle.de \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.