CORE.c.setting.moarvm varies across builds

[bmwiedemann]

The Problem

While working on reproducible builds for openSUSE, I found that our rakudo 2022.07 package varied between builds, even when trying to vary as little as possible.

Expected Behavior

Build outputs should be deterministic

Actual Behavior

/usr/share/perl6/runtime/CORE.c.setting.moarvm varied

Steps to Reproduce

strace tells me, the file is produced by

"/usr/bin/moar" "--libpath=/home/abuild/rpmbuild/BUILD/rakudo-2022.07/blib" "--libpath=/usr/share/nqp/lib" "rakudo.moarvm" "--setting=NULL.c" "--ll-exception" "--optimize=3" "--target=mbc" "--stagestats" "--output=blib/CORE.c.setting.moarvm" "gen/moar/CORE.c.setting"

Environment

• Operating system: openSUSE Tumbleweed 20231013
• Compiler version (rakudo -v or raku -v): 2022.07
• MoarVM-2022.07

[ab5tract]

@bmwiedemann Thanks for reporting this.

Just for clarity, is this an issue that needs to be address for (continued?) inclusion in the openSUSE repos?

[bmwiedemann]

Not today, but long-term (maybe 2025) I'd like to see all our builds reproducible (not yet discussed with the other openSUSE members). We are already at 99% today (by some measure and 97% by another)

The current concept proposes an optional unreproducible repo that could keep packages that are difficult to fix.

[patrickbkr]

Possibly / Probably related: #5099