From: Joshua Watt <jpewhacker@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 3/3] oeqa: reproducible: Do not strip packages
Date: Sun, 19 Jan 2020 12:59:59 -0600 [thread overview]
Message-ID: <20200119185959.406212-4-JPEWhacker@gmail.com> (raw)
In-Reply-To: <20200119185959.406212-1-JPEWhacker@gmail.com>
Do not strip packages when testing reproducible builds. In some cases,
stripped data differs between builds, but then gets removed. However,
the contents affect the generation of the GCC build-id, which then
differs in the resulting ELF files, even though the data that caused
this is no longer there. Inhibit stripping so that their causes can be
evaluated.
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
---
meta/lib/oeqa/selftest/cases/reproducible.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py b/meta/lib/oeqa/selftest/cases/reproducible.py
index c00b92d2e90..34462a0b3a4 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -149,6 +149,7 @@ class ReproducibleTests(OESelftestTestCase):
config = textwrap.dedent('''\
INHERIT += "reproducible_build"
PACKAGE_CLASSES = "{package_classes}"
+ INHIBIT_PACKAGE_STRIP = "1"
TMPDIR = "{tmpdir}"
''').format(package_classes=' '.join('package_%s' % c for c in self.package_classes),
tmpdir=tmpdir)
--
2.24.1
next prev parent reply other threads:[~2020-01-19 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 18:59 [PATCH 0/3] selftest: reproducible: Various improvements Joshua Watt
2020-01-19 18:59 ` [PATCH 1/3] oeqa: reproducible: Add flag for building from sstate Joshua Watt
2020-01-19 18:59 ` [PATCH 2/3] oeqa: reproducible: Fix extra data reporting Joshua Watt
2020-01-19 18:59 ` Joshua Watt [this message]
2020-01-22 15:53 ` [PATCH 3/3] oeqa: reproducible: Do not strip packages Richard Purdie
2020-01-22 16:02 ` Joshua Watt
2020-01-22 16:06 ` Richard Purdie
2020-01-22 18:04 ` Joshua Watt
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=20200119185959.406212-4-JPEWhacker@gmail.com \
--to=jpewhacker@gmail.com \
--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