jj provides prebuilt binaries itself, but only statically linked against musl on linux. Which is fine, because that works on any linux system, whatever the system libc is. However, cargo binstall jj-cli fell back to the (borked) binary provided by quickinstall. I did not notice this at first, even though it does say so in the output of cargo-binstall.
I'm not sure what the right thing to do here is, but having cargo-binstall install from a different source than the official one, even though the official one does in fact provide binaries, is incredibly confusing.
related issue in the jj repo
jj provides prebuilt binaries itself, but only statically linked against musl on linux. Which is fine, because that works on any linux system, whatever the system libc is. However,
cargo binstall jj-cli
fell back to the (borked) binary provided by quickinstall. I did not notice this at first, even though it does say so in the output ofcargo-binstall
.I'm not sure what the right thing to do here is, but having
cargo-binstall
install from a different source than the official one, even though the official one does in fact provide binaries, is incredibly confusing.