-
Notifications
You must be signed in to change notification settings - Fork 1.2k
./gdrive: No such file or directory #597
Comments
same thing here... |
Temporary, You can use wget -q -O /tmp/gdrive.tar.gz "https://github.com/prasmussen/gdrive/releases/download/2.1.1/gdrive_2.1.1_linux_386.tar.gz"
mkdir /tmp/gdrive && tar -xf /tmp/gdrive.tar.gz -C /tmp/gdrive
chmod +x /tmp/gdrive/gdrive
/tmp/gdrive/gdrive download 1o1qjRgkJtnF_8uGB1z6MRsQUjWinHUsw --recursive --path ~/Downloads
|
(Possible reason) The doc say this program is statically linked, which is false on amd64 build . It depends on... musl, and not glibc, which is the default on many linux distro (including ubuntu, arch, etc...). Use the i386 build which is statically linked. |
I confirm that it needs musl, I had the same problem with Arch Linux |
|
|
i spent near one hour to find this problem. @ma3yta yes, thank you i386 binary works just fine. I temporarily using this, any downside compared to amd64? |
@marhensa no downsides. the program just uses 32-bit (i386) CPU instructions instead of 64-bit (amd64) instructions which is OK for x86_64 processors. |
I confirm this bug |
I think we should keep the issue open, until readme atleast mentions this. |
I have the same issue on 2.1.1 |
same issue |
1 similar comment
same issue |
This can be fixed on Debian by command |
on ubuntu x64 22.04 LTS, install musl won't fix this. |
Confirm same issue, on a Linux 3.10 compute cluster. Musl didn't fix, using i386 seems fine. |
Confirm same issue on Ubuntu x86_64 machine Linux 5.15.0-46-generic |
I have extracted gdrive_2.1.1_linux_amd64.tar.gz on my ubuntu 20.04 but when I try to run gdrive with executable permissions I get this error.
The text was updated successfully, but these errors were encountered: