Can't get client executable to run [SOLVED]

Using Linux Mint 10 64-bit, and using the pre-compiled client. When i try to double click on the executable, nothing happens. Don't even get the run in terminal, display, cancel, run choice. When I try to run it in terminal i get the following:

$ ryzom_client ryzom_client: command not found $ ./ryzom_client bash: ./ryzom_client: No such file or directory $ ldd ryzom_client not a dynamic executable

I don't think this is a problem with the executable, cause it's happening with other executables as well, but I figured I'd post here anyways in case one of y'all has any ideas what to do about it.

Replies (6)

RE: Can't get client executable to run - Added by molator over 7 years ago

Are you in the client folder ?
You may have to use:
chmod 755
on the binary.

RE: Can't get client executable to run - Added by Yuritau over 7 years ago

even chmod 777 isn't making a difference.

RE: Can't get client executable to run - Added by Yuritau over 7 years ago

I should add, on my older PC, i installed the 32-bit version of linux mint 10, and then ryzom, and the client had no problem getting to the login screen. Does the client rely on something that 32-bit linux has, and 64-bit doesn't?

RE: Can't get client executable to run - Added by krop over 7 years ago

I don't think this is a problem with the executable, cause it's happening with other executables as well, but I figured I'd post here anyways in case one of y'all has any ideas what to do about it.

Is it installed on a different partition ? Is the partition correctly mounted ? ie, are executables allowed ? check your /etc/fstab

RE: Can't get client executable to run - Added by Yuritau over 7 years ago

it's currently in my /home partition, which is separate from root.

# /home was on /dev/sda6 during installation UUID=758ac313-3dee-448e-a57f-b48cca498305 /home ext4 defaults 0 2

RE: Can't get client executable to run - Added by Yuritau over 7 years ago

Alright, I was pointed to the solution by the folks on the linux mint forums. The problem is the 64-bit OS doesn't by default include some libs from the 32-bit OS, and it's those libs that a bunch of binaries rely on. So a quick sudo apt-get install ia32-libs and everything was working properly!

(1-6/6)