[ev0lution]

Quote:

Originally Posted by Sew_Sumi Again, all of these aren't fixing it... The way to fix it, is to install gcc, and the required runtimes. All you guys are doing is either installing a runtime by fluke, or working around the situation. And really, if this is Frags solution, then they are obviously not too into "hosting" to actually "fix" the issue.

Did you even read the article that I wrote about this problem? It has nothing to do with gcc, you need the correct version of libmysqlclient for your plugin version.

Libmysqlclient is a library that, like many pieces of software, has been updated as time goes on. The MySQL plugin being used by OP was made years ago and depends on libmysqlclient15. That version of libmysqlclient is also >5 years old, and no modern operating system ships with it or has it available in their package manager. Why? Because they make the newest version available, which is libmysqlclient18. Ideally, the MySQL plugin would run with whatever version of libmysqlclient is installed, but it doesn't work like that.

So what are the solutions? Like I wrote, you can:

1. Update the MySQL plugin to a version that isn't >5 years old - the latest version works with the latest version of libmysqlclient. This is also great for security reasons.

2. Use the static version of the MySQL plugin, which basically has libmysqlclient15 built in. Personally I think updating is best, but if you really want to use a plugin that's 5 years old, this is the equivalent of running with libmysqlclient15 installed except it will work on any host without any effort on their part - which also means you don't have to chase around their support/tech teams.

3. Recompile the plugin on a new version of Linux so that it links to libmysqlclient18, the latest version. Most users won't want to do this because it takes a bit more work, but it's a valid solution if you want/need to continue using the old MySQL plugin.

I didn't write this in the article because it's not a great idea - I'm not doing it for FRAG and no other host should - but 4. get the host to find the ancient libmysqlclient15/16 libs and copy them over to all of their servers. Except they're not available from any modern package management sources anymore because they're very old and very out-of-date, so like some of the solutions on this forum you can hunt them down on some dodgy website. Not really something I want to be doing for my hundreds of clients when #2 is essentially the same solution without the security risks of trying to source some ancient library.

I have written the KB article for the benefit of my clients and everyone else on this forum and believe it's technically accurate and offers very good solutions for this problem - which I know is a common one. You haven't told me why it's poor advice or inaccurate yet, but I eagerly await your comments.