ToME: the Tales of Maj'Eyal

Everything about ToME
It is currently Sat Dec 07, 2019 9:20 pm

All times are UTC




Post new topic Reply to topic  [ 19 posts ]  Go to page Previous  1, 2
Author Message
PostPosted: Mon Feb 02, 2015 1:22 am 
Offline

Joined: Mon Feb 02, 2015 1:17 am
Posts: 2
Quote:
Code:
sudo ln -sf /lib/x86_64-linux-gnu/libudev.so.1 /lib/x86_64-linux-gnu/libudev.so.0


Just wanted to post that I had to do this aswell and it worked with

ToME 1.25
Ubuntu 14.04 x64 Fully updated (February 2015)

If you aren't too linux / command line savvy all that is needed

- Extract ToME
- Open terminal, paste and run the above command
- Open game by double clicking t-engine wherever you extracted

Good luck!


Top
 Profile  
 
PostPosted: Tue Feb 03, 2015 12:26 am 
Offline
Wayist

Joined: Tue Jan 27, 2015 6:45 pm
Posts: 22
As far as I can tell, the "real" fix for this should be to offer builds against libudev1 as well as libudev0. Personally, I was afraid of ABI compatibility between the two, so instead of symlinking from one to the other, I built a back-ported libudev0 for Ubuntu 14.10.

Come to think of it, probably including an official libudev0 package for recent Ubuntu releases is the real right fix, but that's out of our control.


Top
 Profile  
 
PostPosted: Tue Feb 03, 2015 9:36 am 
Offline
Master of Eyal

Joined: Wed Jul 24, 2002 9:26 pm
Posts: 10438
Location: Angolwen
Sadly yes :/

Next release will be linked again libudev1; whcih only switches the problem around but heh :/
(and symlinking does work)

_________________
[tome] joylove: You can't just release an expansion like one would release a Kraken XD
--
[tome] phantomfrettchen: your ability not to tease anyone is simply stunning ;)


Top
 Profile  
 
PostPosted: Sun Feb 08, 2015 6:49 am 
Offline
Yeek

Joined: Sat Apr 26, 2014 5:11 pm
Posts: 13
Symlinking affects other programs using libudev.so.0 as well (and libudev.so.0 is not libudev.so.1 even though it's similar enough to make ToME work with it). Making a renamed copy into the specific ToME folder doesn't, as far as I know, so it's better to make a renamed copy. That's what my Gentoo-using programmer friend told me at least.

Another, safer but easy solution:

Workaround on 64-bit:

copy libudev.so.1 from /lib/x86_64-linux-gnu/ to the lib64 directory in your t-engine directory and rename the copy to libudev.so.0. In my case, the t-engine directory is:

/home/user/Desktop/t-engine4-linux64-1.2.5/

So, in my case, I just type this into terminal:

Code:
cp /lib/x86_64-linux-gnu/libudev.so.1 /home/user/Desktop/t-engine4-linux64-1.2.5/lib64/ && cd /home/user/Desktop/t-engine4-linux64-1.2.5/lib64/ && mv libudev.so.1 libudev.so.0


It makes a copy of libudev.so.1 file to t-engine directory and renames the copy in t-engine directory to libudev.so.0. I don't know what libudev.so.x is but it seems libudev.so.1 substitutes libudev.so.0 as long as you rename it to libudev.so.0 to "fool" t-engine to think it is the missing libudev.so.0 by renaming it.

And I can execute t-engine successfully!

On 32-bit, the directory with libudev.so.1 is apparently /lib/i386-linux-gnu/ instead of /lib/x86_64-linux-gnu/


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 19 posts ]  Go to page Previous  1, 2

All times are UTC


Who is online

Users browsing this forum: No registered users and 8 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group