Please provide a statically linked aarch64 version about fd

[tmccombs]

a dynamically linked 32 bits executable might also work?

I'm no expert on ARM, but I think the fd-v9.0.0-arm-unknown-linux-gnueabihf.tar.gz build would be that?

and fd-v9.0.0-arm-unknown-linux-musleabihf.tar.gz would be a statically compiled 32-bit arm version.

A statically linked version might be as simple as adding a line like

          - { target: aarch64-unknown-linux-musl  , os: ubuntu-20.04, use-cross: true }

to the build matrix. But I'm not sure if there would be any problems with that, and don't have a way to test if it works.

[pro-sumer]

I'm not sure, but it looks like I have a 64 bits executable and 32 bits library?

If true, a dynamically linked 32 bits executable might also work? (As an alternative solution)

[pro-sumer]

fd-v9.0.0-arm-unknown-linux-musleabihf.tar.gz would be a statically compiled 32-bit arm version.

I already tried that, but:

➜ ./fd
zsh: illegal hardware instruction  ./fd

[pro-sumer]

A statically linked version might be as simple as adding a line like ... to the build matrix. But I'm not sure if there would be any problems with that, and don't have a way to test if it works.

Excellent suggestion! (I wasn't aware that the executables were built using GitHub actions)

I forked the repo, created a branch, added that line, and tested the generated binary on my router. Result:

➜ fd --version
fd 9.0.0

The statically linked aarch64 version works!

[pro-sumer]

Created PR #1478 to add this target (if @sharkdp approves such an addition).