🇳🇱
Dumb ass Linux problem... like really dumb...
So I clearly have this file in my directory and it is set as executable (pastebin at the bottom)... Yet when i try to run it im told the file doesnt exist... how is this possible....
@realcaseyrollins if it were a symlink the the ls -lha should show it... i doubt the subdirectories are symlinks but ill double check.
Corrupted harddrive is possible I suppose but if thats the case this is the only symptom so far.
Could this be the issue?
"If the file does exist in that for (no funny characters), one other possibility is that you're trying to run a 32-bit ELF program on a system that's not correctly set up to run them (i.e., a 64-bit system without the libraries and support infrastructure for 32-bit)."
From:
https://stackoverflow.com/questions/48179399/zsh-no-such-file-or-directory-error-but-file-exist
That sounds like a distinct possiblity yea.. this program was pre-compiled when i downloaded it... That said its a java program behind the scenes.. .this precompiled binary is some sort of launcher or installer or something....
Are you familiar with 'file' on the command line?
> file name-of-file
should give you a decent amount of useful info about it
@chris_spackman yes i shared that output later i the thread, take a look
Oops, user mastodon error - wasn't looking at the full thread. My bad.
Looking at the full thread ....
.... I'm all out of ideas.
@freemo What interpreter does that file reference? Is there a #! ? Is the path to it correct?
@bac The file itself is binary, i cant see.. but it came with a shell script which is supposed to launch it (it doesnt) which uses bash interpriter.
@freemo What happens if you use ld.so to execute the file?
$ ld.so ./QuPath
With older glibc versions you'd have to use /lib64/ld-linux-x86-64.so.2 instead.
@ixn when I run that command it just returns with no outut... hmmm
@freemo Hmm...perhaps there's a symlink issue happening? Or your hard drive is corrupted somehow? I came across something similar once when trying to delete files off my #PLEX server once, turned out there was a weird symlink thing caused by corrupted sectors on the drive