-
-
Notifications
You must be signed in to change notification settings - Fork 785
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please provide a statically linked aarch64 version #1477
Comments
If true, a dynamically linked 32 bits executable might also work? (As an alternative solution) |
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
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. |
I already tried that, but:
|
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:
The statically linked aarch64 version works! |
Thank you for creating
fd
! A great tool, that I run on my Mac and Raspberry Pi's. I want to run it on my router as well, but that fails:My router is an ASUS ROG GT-AX6000 with the excellent third-party Asuswrt-Merlin firmware installed. I use the Entware repository for embedded devices to install additional software. Unfortunately
fd
is not included (that would actually be the best solution for me), but they do include libgcc (currently 8.4.0-11). I manually installed fd-v9.0.0-aarch64-unknown-linux-gnu.tar.gz, which seems to start, but fails with the error above.I'm not sure, but it looks like I have a 64 bits executable and 32 bits library?
If so, would it be possible to publish a statically linked version of the
aarch64
flavour offd
? (which contains the 64 bits version of libgcc)The text was updated successfully, but these errors were encountered: