From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: docs@lists.yoctoproject.org, tonyb@cybernetics.com
Subject: Re: [docs] [PATCH] test-manual: document LTO related reproducibility bug
Date: Fri, 23 Jul 2021 15:19:25 +0200 [thread overview]
Message-ID: <bb1efba1-7335-fb00-e133-5562eca438f9@bootlin.com> (raw)
In-Reply-To: <1692572BA30A3D60.32208@lists.yoctoproject.org>
On 7/16/21 7:57 PM, Michael Opdenacker wrote:
> 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>`.
Merged into "master-next" for yocto-docs, after replacing "a Makefile"
by "CFLAGS", as recommended by Tony (thanks!)
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
parent reply other threads:[~2021-07-23 13:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1692572BA30A3D60.32208@lists.yoctoproject.org>]
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=bb1efba1-7335-fb00-e133-5562eca438f9@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