From: Alexander Kanavin <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex@linutronix.de>
Subject: [PATCH 1/6] go: log build id computations
Date: Sat, 1 Jan 2022 12:29:54 +0100 [thread overview]
Message-ID: <20220101112959.1866747-1-alex@linutronix.de> (raw)
go writes build-specific ids into binaries it produces
and has a custom system for calculating them from
file hashes, environment variables and other inputs
(not that dissimilar to sstate cache, actually). This can
go wrong :) in various ways (for purposes of reproducibility
in particular), so this enables useful logs to see what
happens and why.
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
meta/classes/go.bbclass | 2 ++
meta/recipes-devtools/go/go-common.inc | 2 ++
2 files changed, 4 insertions(+)
diff --git a/meta/classes/go.bbclass b/meta/classes/go.bbclass
index aa54b4a08c..5c1fdd7d5f 100644
--- a/meta/classes/go.bbclass
+++ b/meta/classes/go.bbclass
@@ -2,6 +2,8 @@ inherit goarch
GO_PARALLEL_BUILD ?= "${@oe.utils.parallel_make_argument(d, '-p %d')}"
+export GODEBUG = "gocachehash=1"
+
GOROOT:class-native = "${STAGING_LIBDIR_NATIVE}/go"
GOROOT:class-nativesdk = "${STAGING_DIR_TARGET}${libdir}/go"
GOROOT = "${STAGING_LIBDIR}/go"
diff --git a/meta/recipes-devtools/go/go-common.inc b/meta/recipes-devtools/go/go-common.inc
index dfccebdb83..5bbf35b787 100644
--- a/meta/recipes-devtools/go/go-common.inc
+++ b/meta/recipes-devtools/go/go-common.inc
@@ -37,6 +37,8 @@ export GO386 ?= "${TARGET_GO386}"
export GOMIPS ?= "${TARGET_GOMIPS}"
export GOROOT_FINAL ?= "${libdir}/go"
+export GODEBUG = "gocachehash=1"
+
do_compile:prepend() {
BUILD_CC=${BUILD_CC}
}
--
2.20.1
next reply other threads:[~2022-01-01 11:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 11:29 Alexander Kanavin [this message]
2022-01-01 11:29 ` [PATCH 2/6] lib/oe/reproducible: correctly set .git location when recursively looking for git repos Alexander Kanavin
2022-01-01 11:29 ` [PATCH 3/6] go: correctly set debug-prefix-map and build directory Alexander Kanavin
2022-01-10 4:34 ` [OE-core] " Dmitry Baryshkov
2022-01-10 8:08 ` Alexander Kanavin
2022-01-12 14:47 ` Dmitry Baryshkov
2022-01-12 14:55 ` Dmitry Baryshkov
2022-01-12 15:00 ` Alexander Kanavin
2022-01-12 15:07 ` Otavio Salvador
[not found] ` <16C98DFE7ACD4942.29114@lists.openembedded.org>
2022-01-12 15:07 ` Alexander Kanavin
2022-01-01 11:29 ` [PATCH 4/6] go-runtime.inc: do not make installation set dependent on host Alexander Kanavin
2022-01-02 12:39 ` [OE-core] " Matt Madison
2022-01-02 16:30 ` Alexander Kanavin
[not found] ` <16C6811541A7227F.5913@lists.openembedded.org>
2022-01-02 18:13 ` Alexander Kanavin
2022-01-01 11:29 ` [PATCH 5/6] go: additional patches to help reproducibility Alexander Kanavin
2022-01-01 11:29 ` [PATCH 6/6] selftest/reproducible: drop go items from exception list Alexander Kanavin
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=20220101112959.1866747-1-alex@linutronix.de \
--to=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=openembedded-core@lists.openembedded.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