View Full Version : 64bit linux (Suse) cannot find libhal.so when running ./rolauncher
Heiios1
06-04-2011, 04:14 AM
When I try to run ./rolauncher I get the following errors. The login screen pops up, when as soon as I login the game dies.
/home/user/bin/regnum$ ./rolauncher
libhal.so: cannot open shared object file: No such file or directory
libhal-storage.so: cannot open shared object file: No such file or directory
I'm running 64-bit openSuse. I have the following symbolic links setup in my /usr/lib/ directory
sudo ln -s libhal.so.1.0.0 libhal.so
sudo ln -s libhal-storage.so.1.0.0 libhal-storage.so
But still no luck
Znurre
06-04-2011, 08:22 AM
Check your /usr/lib64 instead, I think that's where your 64 bit libs are stored in openSUSE.
Because I take it you're using the 64-bit version of Regnum?
Topogigio_BR
06-04-2011, 10:01 AM
I was with Opensuse 11.4 (64-bits) a while a go and the only problem i had was with libpng12, due to some erros in launcher compilation that, i thinki, NGD have already solved.
Heiios1
06-04-2011, 04:58 PM
Check your /usr/lib64 instead, I think that's where your 64 bit libs are stored in openSUSE.
Because I take it you're using the 64-bit version of Regnum?
Thats a great idea, I didnt think of it.
Should I create a symbolic link in the /usr/lib64 to point to the libhal.so.1.0.0.0 in the /user/lib directory?
Eh that didnt work, when I created the new sym link I get this now
libhal.so: wrong ELF class: ELFCLASS32
libhal-storage.so: wrong ELF class: ELFCLASS32
The program 'rolauncher' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 32 error_code 3 request_code 138 minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Maybe I should just go with the 32 bit version...?
Znurre
06-04-2011, 05:14 PM
You need the 64-bit version of those libraries installed.
That will solve the problem.
Heiios1
06-06-2011, 11:09 PM
You need the 64-bit version of those libraries installed.
That will solve the problem.
Thanks, that solved this issue.
I'll start a new thread with the next issue. Thanks again
vBulletin® v3.8.7, Copyright ©2000-2024, vBulletin Solutions, Inc.