slackware doesn't recognize an executable

Cultist · 07-27-2010, 09:47 PM

there's a program I have that doesn't really install, you extract it to its folder, cd into it, then ./filename to start it. It works fine on my Debian install. But when I do this on Slackware, it just says 'no such file or directory'. The file most definitely is there, since ls shows it. the filename is only three letters long so I know I'm not mistyping it. I've tried in user and su. Any idea why it won't run?

hitest · 07-27-2010, 09:53 PM

What program are you trying to install?

Cultist · 07-27-2010, 09:54 PM

its pSX, a Playstation emulator. It doesn't need to compile or install, it runs right out of the folder. Which is why I find it odd that it won't work in Slackware while working on Debian.

hitest · 07-27-2010, 10:12 PM

Quote:

Originally Posted by Cultist

its pSX, a Playstation emulator. It doesn't need to compile or install, it runs right out of the folder. Which is why I find it odd that it won't work in Slackware while working on Debian.

I would guess that you are missing some dependencies in Slackware (possibly Gnome related) that are preventing the program from running. Try to find out what the program needs to run.

Cultist · 07-27-2010, 10:14 PM

dependencies shouldn't keep it from running at all, though. In Debian, it ran but gave me dependency errors til I fixed them, then it worked. In Slackware it just says that the file I'm trying to run doesn't exist.

T3slider · 07-27-2010, 10:22 PM

Are you running a 32-bit executable on a 64-bit installation? `file filename` should tell you...

If you want to get a 32-bit executable running on Slackware64 then you would need Alien Bob's multilib stuff.

Cultist · 07-27-2010, 10:24 PM

yeah its a 32 bit app and I'm on a 64bit slackware, which is why it gave so much trouble in Debian

T3slider · 07-27-2010, 10:54 PM

See here for how to make Slackware64 multilib. Without it you will never get that app running, unless there is a 64-bit version.

Skaperen · 07-28-2010, 10:23 AM

Quote:

Originally Posted by T3slider

See here for how to make Slackware64 multilib. Without it you will never get that app running, unless there is a 64-bit version.

Now, the next step is to make your Slackware system one which can BUILD an application from source (maybe one you are developing) into both 32-bit and 64-bit Slackware packages, on the one machine (instead of doing parallel builds on separate Slackware(32) and Slackware64 systems).

ringwraith · 07-28-2010, 10:47 AM

You may also want to check the perms to be sure it is marked executable.

Cultist · 07-28-2010, 06:14 PM

well, the app is closed-source, so I'm not compiling anything. It literally just runs off a file that untars in /home.

Would the multilib issue cause the file to not even be recognized as existing?
I made sure that its set to be executable, and using the icon does nothing, while trying to run in konsole just produces the No Such File Or Directory.

T3slider · 07-28-2010, 06:29 PM

Quote:

Originally Posted by Cultist

Would the multilib issue cause the file to not even be recognized as existing?

Yes. Assuming the file is executable and you are running it properly, if there is an architecture mismatch it reports a missing file since it cannot find a properly executable command with that filename on the current system.

bgeddy · 07-28-2010, 06:29 PM

You are trying to execute a 32 bit application on a 64 bit OS. The message is standard when doing this. As T3slider has told you - run file "file $filename" replacing filename with your faulty executable to confirm.

2 to ensure.

Daedra · 07-28-2010, 06:29 PM

Another program you could try is pcsxr, I use it and it works great. It's available over at http://slackbuilds.org/repository/13.1/games/pcsxr/ plus it runs natively in 64bit so you wont need the multilib packages to make it work.

Cultist · 07-28-2010, 06:32 PM

well crap. I was hoping to not have to do any major reconfigs to make this work. Thanks for the link though