pslaunch.bin: No such file or directory

[jowifi]

I just downloaded 0.5.4 for 64 bit Linux. I keep getting the following error when I try to launch pslaunch.

Code: [Select]

./pslaunch: line 5: /opt/PlaneShift/pslaunch.bin: No such file or directory
./pslaunch: line 5: /opt/PlaneShift/pslaunch.bin: Success
psclient produces the same results.

It doesn't matter what command line options I pass.  I've tried installing as root (system wide and not) and as user.  I've tried tweaking file permissions.

Running on Mandriva 2010.0 64-bit, BFG 6800 OC with nvidia proprietary drivers.

[assaulth3ro911]

I am not sure if this is for your Linux OS, can you link me to your operating system's main site?

[jowifi]

Link to Mandriva main site:  http://www2.mandriva.com/

Is there any way to figure out what files pslaunch is looking for and where it's expecting to find them?

[RlyDontKnow]

it expects pslaunch (the shell script) to be in the same dir as pslaunch.bin which shall be the same dir as that of vfs.cfg
in your case I'd say make sure you really have the right version.
i.e. "uname -m" should output x86_64. if it outputs ix86 (e.g. i686), you have to use the 32bit version which would explain your issue.
also make sure ld-linux-x86-64.so.2 is located in /lib (if it isn't, create a symlink to that location, e.g. ln -s /actual/path/ld-linux-x86-64.so.2 /lib/ld-linux-x86-64.so.2)

[Lirrec]

I have the same problem on 64Bit Opensuse.

Code: [Select]

ln -s /lib64/ld-linux-x86-64.so.2 /lib/ld-linux-x86-64.so.2
made it start. (thx RlyDontKnow)
This seems to be some misconfiguration with the binaries, because the x86_64 ld-libs are on my System in /lib64, not in /lib

[jowifi]

Adding the symlink in /lib  to /lib64/ld-linux-x86-64.so.2 solved the problem.  Thanks.

[J0nnJ0nes]

Thank you for the workaround, but it should be fixed in the source code, shouldn't it? Please do look into it, as multi-platform compatibility is essential.

[weltall]

it's not a source issue it's a build issue it seems 1 or 2 major distro over all the ones out don't symlink that file there creating the problem