File ipxe.stable-build-id.patch of Package xen

Overview Repositories Revisions Requests Users Attributes Meta

File ipxe.stable-build-id.patch of Package xen (Revision f61ba3b00a8cabe4672b4063a162ac2c)

Currently displaying revision f61ba3b00a8cabe4672b4063a162ac2c , Show latest

From: Olaf Hering <olaf@aepfle.de>
Date: Thu, 19 Jan 2017 10:36:38 +0100
Subject: stable build-id

It is desirable to produce the same bits on subsequent
builds when the actual code of the package doesn't
change. (bsc#1011213)

Signed-off-by: Bruce Rogers <brogers@suse.com>
---
 src/Makefile.housekeeping | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

--- a/src/Makefile.housekeeping
+++ b/src/Makefile.housekeeping
@@ -780,7 +780,11 @@ blib : $(BLIB)
 # Command to generate build ID.  Must be unique for each $(BIN)/%.tmp,
 # even within the same build run.
 #
-BUILD_ID_CMD	:= perl -e 'printf "0x%08x", int ( rand ( 0xffffffff ) );'
+# NB: In the case of the SUSE ipxe package we want reproducible
+# builds, so we just use the TGT_PCI_VENDOR variable, which is already
+# a unique (in the context of the files we generate) hex value suitable
+# for specifying the build_id. We no longer define a BUILD_ID_CMD, as
+# we need to use the TGT_PCI_VENDOR variable directly in the link command
 
 # Build an intermediate object file from the objects required for the
 # specified target.
@@ -788,7 +792,7 @@ BUILD_ID_CMD	:= perl -e 'printf "0x%08x", int ( rand ( 0xffffffff ) );'
 $(BIN)/%.tmp : $(BLIB) $(MAKEDEPS) $(LDSCRIPT)
 	$(QM)$(ECHO) "  [LD] $@"
 	$(Q)$(LD) $(LDFLAGS) -T $(LDSCRIPT) $(TGT_LD_FLAGS) $(BLIB) -o $@ \
-		--defsym _build_id=`$(BUILD_ID_CMD)` -Map $(BIN)/$*.tmp.map
+		--defsym _build_id="$(TGT_PCI_VENDOR)" -Map $(BIN)/$*.tmp.map
 	$(Q)$(OBJDUMP) -ht $@ | $(PERL) $(SORTOBJDUMP) >> $(BIN)/$*.tmp.map
 
 # Keep intermediate object file (useful for debugging)

Places

File ipxe.stable-build-id.patch of Package xen (Revision f61ba3b00a8cabe4672b4063a162ac2c)

Places