From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: docs@lists.yoctoproject.org, tonyb@cybernetics.com
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH] test-manual: document LTO related reproducibility bug
Date: Fri, 16 Jul 2021 19:57:25 +0200 [thread overview]
Message-ID: <20210716175725.99486-1-michael.opdenacker@bootlin.com> (raw)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/test-manual/reproducible-builds.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/documentation/test-manual/reproducible-builds.rst b/documentation/test-manual/reproducible-builds.rst
index e13583c0bf..1938041b2d 100644
--- a/documentation/test-manual/reproducible-builds.rst
+++ b/documentation/test-manual/reproducible-builds.rst
@@ -68,6 +68,17 @@ things we do within the build system to ensure reproducibility include:
- Filtering the tools available from the host's ``PATH`` to only a specific set
of tools, set using the :term:`HOSTTOOLS` variable.
+.. note::
+
+ Because of an open bug in GCC, using ``DISTRO_FEATURES_append = " lto"`` or
+ adding ``-flto`` (Link Time Optimization) to a Makefile makes the resulting
+ binary non-reproducible, in that it depends on the full absolute build path
+ to ``recipe-sysroot-native``, so installing the Yocto Project in a different
+ directory results in a different binary.
+
+ This issue is addressed by
+ :yocto_bugs:`bug 14481 - Programs built with -flto are not reproducible</show_bug.cgi?id=14481>`.
+
=========================================
Can we prove the project is reproducible?
=========================================
--
2.25.1
reply other threads:[~2021-07-16 17:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210716175725.99486-1-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=tonyb@cybernetics.com \
/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