Open filbranden opened 1 month ago
Thanks for the report! This is a really unfortunate issue, although a known one (#873). We build these binaries internally on machines where we don't control the build toolchain. We need to move these builds, but haven't prioritized that work yet. Honestly it kind of fell off my radar, so I'll take another look today.
Thank you!
If I can make a suggestion, building in a container should be a good way to get reproducible builds without having the underlying host environment affect your system. Happy to provide you with a PR to build in a container in GitHub Actions if you'd like that (but it seems you moved away from GitHub Actions for a reason, so not sure if that's what you're looking for.)
Cheers!
Pyre Bug
Bug description Latest pyre versions 0.9.21 and 0.9.22 from PyPI do not work on Debian Bullseye with glibc 2.31
Reproduction steps
Expected behavior Expecting the binary to work, as it does on 0.9.19
Logs
Output of
pyre rage
:Additional context
Probably related to a build environment or ocaml compiler used during builds, regression seemed to be introduced between 0.9.19 and 0.9.21