Make build artifacts reproducible

[fmeum]

No description provided.

[fmeum]

@illicitonion

[fmeum]

Should we also sync in the recent upstream changes? bazel-contrib...richard-vd:musl-cross-make:master

[illicitonion]

Should we also sync in the recent upstream changes? bazel-contrib...richard-vd:musl-cross-make:master

Sounds good! Want to maybe create a PR with a merge commit, and if it passes CI we can just force-push a rebase?

[illicitonion]

Thanks!

[fmeum]

I'm a bit confused - are we tracking https://github.com/richard-vd/musl-cross-make, which in turn is tracking https://github.com/richfelker/musl-cross-make? The last one appears to be more active, but also has more conflicts.

[illicitonion]

I'm a bit confused - are we tracking https://github.com/richard-vd/musl-cross-make, which in turn is tracking https://github.com/richfelker/musl-cross-make? The last one appears to be more active, but also has more conflicts.

I believe the intention is to track https://github.com/richfelker/musl-cross-make with a cherry-pick of richfelker#129 - we were tracking https://github.com/richard-vd/musl-cross-make because it had the cherry-picks, but it would be reasonable to rebase on richfelker with those cherry-picks, rather than being based on the richard-vd fork.