On 11/26/20 12:07 PM, Joe Pfeiffer wrote:
Fred <f...@blakemfg.com> writes:
On 11/26/20 9:04 AM, Joe Pfeiffer wrote:
Fred <f...@blakemfg.com> writes:
On 11/25/20 12:30 PM, Reco wrote:
Hi.
On Wed, Nov 25, 2020 at 12:13:03PM -0700, Fred wrote:
fred@ragnok:~$ ./ClipGrab-3.9.2-x86_64.AppImage --help
bash: ./ClipGrab-3.9.2-x86_64.AppImage: cannot execute binary file: Exec format
error
uname -m
Reco
fred@ragnok:~$ uname -m
i686
fred@ragnok:~$ file ClipGrab-3.9.2-x86_64.AppImage
ClipGrab-3.9.2-x86_64.AppImage: ELF 64-bit LSB executable, x86-64,
version 1 (SYSV), dynamically linked, interpreter
/lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, stripped
Your uname says you are running a 32-bit system (686 is 32 bit). The
output from the file command says it's a 64 bit executable. You can run
a 32 bit executable on a 64 bit system, but you can't run a 64 bit
executable on a 32 bit system.
Yes, I see that now. I thought I was running 64 bit.
fred@ragnok:~$ lscpu
Architecture: i686
CPU op-mode(s): 32-bit, 64-bit
This seems to say the cpu will run 64 bit software.
I suspect (so I'm not sure) that that this means you've got a cpu that
is physically capable of running in 64 bit mode, but you installed a
in i686 operating system so only the 32 bit mode is actually available
to you. It would be interesting to run uname as
uname -a
and see what it tells you. In my case I get
Linux snowball 5.8.0-2-amd64 #1 SMP Debian 5.8.10-1 (2020-09-19) x86_64
GNU/Linux
I'll hazard a guess that the places that say amd64 and x86_64 will say
things related to i686 instead.
You are correct of course. I thought I was running 64 bit but I was wrong.
fred@ragnok:~$ uname -a
Linux ragnok 4.19.0-12-686-pae #1 SMP Debian 4.19.152-1 (2020-10-18)
i686 GNU/Linux
I have abandoned trying to run the 64 bit clipgrab binary blob.
youtube-dl is working now and I plan to install the 64 bit version of
Devuan when I have time.
Best regards,
Fred
