From df56d7c525af57bf7a2378a1e9bf69d78fee56a3 Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Wed, 25 Oct 2023 16:54:16 +0200 Subject: test-manual: reproducible-builds: stop mentioning LTO bug Now that https://bugzilla.yoctoproject.org/show_bug.cgi?id=14481 is closed. (From yocto-docs rev: 260b446a1a75d99399a3421cd8d6ba276f508f37) Signed-off-by: Michael Opdenacker Signed-off-by: Steve Sakoman --- documentation/test-manual/reproducible-builds.rst | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/documentation/test-manual/reproducible-builds.rst b/documentation/test-manual/reproducible-builds.rst index 5977366c9e..6994989f7c 100644 --- a/documentation/test-manual/reproducible-builds.rst +++ b/documentation/test-manual/reproducible-builds.rst @@ -68,17 +68,6 @@ 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 ``CFLAGS`` 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`. - ========================================= Can we prove the project is reproducible? ========================================= -- cgit v1.2.3-54-g00ecf