A non-deterministic value is set in /usr/include/pike8.0/pike/machine.h
based on some build time tests from configure:
#define FB_CPU_TIME_IS_THREAD_LOCAL PIKE_UNKNOWN
vs.
#define FB_CPU_TIME_IS_THREAD_LOCAL PIKE_NO
I have attached a workaround patch to debian/rules which disables
threading, which does not trigger this codepath...
Understandably, threading may be highly desired and so this may not be
an appropriate way to fix the issue.
I am not familiar with the pike8.0 codebase, but maybe someone who is
would have a better idea of a proper fix.
Ideally, these tests should be done at runtime instead of relying on the
build machine's cpu characteristics, timing and possibly system load at
the time of the build, or maybe the appropriate
lowest-common-denominator value should be forced in the Debian
packaging.
Unfortunately, this patch alone does not solve all reproducibility
issues with pike8.0, but applying this patch should reduce the
differences, making it easier to debug remaining issues.
Thanks for maintaining pike8.0!
live well,
vagrant