reproducible builds issue #230
Comments
|
Rust projects will always have different binaries when building with a different number of codegen units. You can configure your build system to 1 if you want it to use only one. |
bmwiedemann
added a commit
to bmwiedemann/launcher
that referenced
this issue
Jul 31, 2024
as suggested in https://nnethercote.github.io/perf-book/build-configuration.html#codegen-units to achieve reproducible builds. It can also enhance optimizations of the produced binary. Fixes pop-os#230 This patch was done while working on reproducible builds for openSUSE, sponsored by the NLnet NGI0 fund.
|
Indeed. #231 seems to avoid that issue. Others do the same already: |
bmwiedemann
added a commit
to bmwiedemann/launcher
that referenced
this issue
Jul 31, 2024
as suggested in https://nnethercote.github.io/perf-book/build-configuration.html#codegen-units to achieve reproducible builds. It can also enhance optimizations of the produced binary. Fixes pop-os#230 This patch was done while working on reproducible builds for openSUSE, sponsored by the NLnet NGI0 fund.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While working on reproducible builds for openSUSE (sponsored by the NLnet NGI0 fund), I found that our
pop-launcherpackage build produces different results between a 1-core-VM and a VM with 2+ cores. This could be an indicator of some race-condition or poorly defined build-dependencies.https://rb.zq1.de/other/pop-launcher/strings.diff.txt
shows that some symbols have variations in the ID at the end.
e.g.
The two full binaries are also available in the same directory.
The text was updated successfully, but these errors were encountered: