bigtools
bigtools copied to clipboard
Consider distributing release artifacts built against an older GLIBC (2.28)
By default, the current github release artifacts don't work on our cluster, because it needs GLIBC 2.29 or newer, but the cluster's GLIBC version is 2.28. I suspect other clusters will also be similarly older, so probably makes sense to build against an older GLIBC. Alternatively (or in addition), could consider building a -musl artifact.
@jackh726 I build most rust software with cargo zigbuild to target older glibc versions (2.17 in this case). Musl builds are in general way slower if progams do a lot of memory allocations:
PATH=/software/zig/zig-linux-x86_64-0.14.1:$PATH cargo zigbuild --target x86_64-unknown-linux-gnu.2.17 --release