I'm running DreamDaemon a Debian VPS and attempting to use dantom.db on it. However, after invoking error output, I get this:
libmariadb.so: cannot open shared object file: No such file or directory
Which is weird, since I double and triple-checked that libmariadb.so was in /usr/local/byond/bin. I set the file's permission to rwxr-xr-x as well, making sure anything can at least execute the .so. Still does not work, however.
Anyone more experienced with this willing to lend a hand?
1
2
ID:1887571
Jul 2 2015, 3:54 pm
|
|
Jul 2 2015, 4:37 pm
|
|
What version of debian have you got, and what architecture?
|
Man, that's awkward. Basically I don't think anyone's backported libmariadb-client-dev or similar onto 6.0 (squeeze). Would you mind going for the actual MySQL shared object instead, as that's available on squeeze, or do you need MariaDB shared objects specifically?
Where did you get libmariadb.so from? |
I got libmariadb.so from the MariaDB website: https://mariadb.org
Where exactly can I find the actual mysql so? I don't specifically need MariaDB. |
Ahhh, actually, MariaDB has their own repo:
https://downloads.mariadb.org/mariadb/ repositories/#mirror=coreix&distro=Debian&distro_release=squ eeze--debian6&version=10.0 Install that, then: apt-get install libmariadbclient18:i386 This provides you with: /usr/lib32/libmysqlclient.so.18 Which hopefully BYOND will load up okay. |
Your original problem (aside from the slightly janky install location) is probably that you picked up the 64 bit library, and BYOND itself is 32 bit. As such, BYOND can only load 32 bit shared objects.
|
apt-get install libmariadbclient18:i386
After doing everything on that page you linked, gives me: E: Unable to locate package libmariadbclient18:i386 |
Oh, right. Now I remember. I actually downloaded the .so I was using from a link in the Dantom.db page itself:
http://www.byond.com/developer/Dantom/DB |
When you add the repo
https://downloads.mariadb.org/mariadb/ repositories/#mirror=coreix&distro=Debian&distro_release=squ eeze--debian6&version=10.0 Make sure you update the packages in apt, before attempting to install.. apt-get update |
In response to A.T.H.K
|
|
You mean after I do this step:
Right? Because I've already performed apt-get update afterward. |
Correct.
If that's the case run apt-cache search libmariadb* I've gotten the below results, > @byondpanel:~# apt-cache search libmaria And the below for apt-get install @byondpanel:~# apt-get install libmariadbclient18:i386 Just to aviod confusion, I'm currently on Wheezy and used the repo for Squeeze, hence that error. |
You sure you're on 64bit?
Below forces 32bit installs on 64bit arch apt-get install libmariadbclient18:i386 Below is just the normal package, 32 or 64. apt-get install libmariadbclient18 |
It says I'm running 64-bit...
Also, apt-get install libmariadbclient18 seemed to work. Weeeeird. |
Unfortunately that .so did not work either.
Since I messed up my previous mysql install, I decided to just format the drive and begin anew (this time using Debian 8). Of course, my issue's still there. Any further advice? |
apt-get install libmariadb2:i386
on Debian jessie. You shouldn't really even need the mariadb repository. The fundamental problem is quite simple, APT will by default install libraries for your architecture (x86_64), and BYOND is an i386 application, so it cannot use those libraries. What you may need to check, following a successful install of the above, is that the following exists: /usr/lib32/libmariadb.so If it doesn't, then a symlink would do: ln -s /usr/lib/i386-linux-gnu/libmariadb.so.2 /usr/lib32/libmariadb.so |
Thankfully those instructions work, however, attempting to use the libmariadb.so file it outputs yields the same results. It's unable to locate / execute the file (permissions properly set).
|
I don't know about you two, or Mariadb but with MySQL I always got that unless I installed libmysqlclient-dev then it just worked out of the box..
MySql and DD that is... Since Mariadb is a spin off of MySQL it may work.. |
Sorry for the absence.
Running: apt-get install libmysqlclient-dev Yielded no results as well. At this point I'm considering just defaulting to Windows Server, since nothing at this point seems to work... and I've tried so many things now, not limited to the things in this thread. |
1
2