Jump to content
Eternal Lands Official Forums
Sign in to follow this  
lord_henry

el 130 on Debian Sarge

Recommended Posts

Hello,

 

I am afraid that you accidently banned Debian Sarge users from Eternal Lands.

But have a look for yourself:

me@computer:~/el$ ./el-130.x86.linux.bin

./el-130.x86.linux.bin: error while loading shared libraries:

libcal3d.so.11: cannot open shared object file: No such file or directory

 

libcal3d.so.11 is not part of Debian Sarge. It will be Included with

Debian Etch. But so long we only have libcal3d.so.10

 

Can you provide a workaround or a Sarge Version/Patch for eternal lands.

Henry

Share this post


Link to post
Share on other sites

Hello,

 

I am afraid that you accidently banned Debian Sarge users from Eternal Lands.

But have a look for yourself:

me@computer:~/el$ ./el-130.x86.linux.bin

./el-130.x86.linux.bin: error while loading shared libraries:

libcal3d.so.11: cannot open shared object file: No such file or directory

 

libcal3d.so.11 is not part of Debian Sarge. It will be Included with

Debian Etch. But so long we only have libcal3d.so.10

 

Can you provide a workaround or a Sarge Version/Patch for eternal lands.

Henry

There is a static version that should work for you already include in the .zip file. Try that and see if it fixes your problems.

Share this post


Link to post
Share on other sites

Now I have the following situation:

wichtig.png

 

EL, anounces that it cannot resolve the Server adress.

 

What can I do?

 

I checked the config files, traced the server and tracing worked.

 

There is no problem with my DNS, I can still resolve hostnames.

 

Thank you very much,

Henry

Share this post


Link to post
Share on other sites

try opening ~/.elc/el.ini (not the one that's in your install dir) and see if the #server_address is set wrong.

if it's correct, try changing it to the IP address and see if that fixes it

Share this post


Link to post
Share on other sites
The configuration was not proper (didn't know it was in my home dir, because there was one in the binary's dir).
yeah, that has caught quite a few people. that's what the one in hoimedir is made from, though, and is used in windows, so the problem probably won't go away any time soon ;)
Well this did the trick.
nifty

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×