diff options
| -rw-r--r-- | documentation/test-manual/reproducible-builds.rst | 11 |
1 files changed, 0 insertions, 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: | |||
| 68 | - Filtering the tools available from the host's ``PATH`` to only a specific set | 68 | - Filtering the tools available from the host's ``PATH`` to only a specific set |
| 69 | of tools, set using the :term:`HOSTTOOLS` variable. | 69 | of tools, set using the :term:`HOSTTOOLS` variable. |
| 70 | 70 | ||
| 71 | .. note:: | ||
| 72 | |||
| 73 | Because of an open bug in GCC, using ``DISTRO_FEATURES:append = " lto"`` or | ||
| 74 | adding ``-flto`` (Link Time Optimization) to ``CFLAGS`` makes the resulting | ||
| 75 | binary non-reproducible, in that it depends on the full absolute build path | ||
| 76 | to ``recipe-sysroot-native``, so installing the Yocto Project in a different | ||
| 77 | directory results in a different binary. | ||
| 78 | |||
| 79 | This issue is addressed by | ||
| 80 | :yocto_bugs:`bug 14481 - Programs built with -flto are not reproducible</show_bug.cgi?id=14481>`. | ||
| 81 | |||
| 82 | ========================================= | 71 | ========================================= |
| 83 | Can we prove the project is reproducible? | 72 | Can we prove the project is reproducible? |
| 84 | ========================================= | 73 | ========================================= |
