mariadb-5.5 | TokuDB for MariaDB | SQL Database library

The maintainers of FOSS software, in this case the MariaDB Foundation, usually don't make promises that download URLS will remain unchanged. MariaDB uses a scheme to help downloaders find a nearby mirror site, and that's what you found.

Those mirrorfinders rely on stuff like http redirect operations. Browsers are good at handling those operations. Downloading code built into other programs may not be.

You may find it helpful to edit that URL in that recipe to point to the exact ftp file you need. It appears to be in this ftp folder.

I'm wondering if anyone else has attempted to compile towards mysqlclient and run on a separate machine with success.

People do that routinely. It is the basis for packaging systems such as RPM. People also do it for dissimilar systems, which is called "cross compiling".

What is not so common is compiling for a system with one version of a given OS and expecting the result to work on systems with earlier versions of that OS. Under some circumstances that can work, but people who want to support multiple versions of an OS without separate compilation typically approach it by compiling for the earlier version, not the latter. This presents fewer compatibility problems, and those that arise are usually easier to resolve.

Note that we've tried linking towards and delivering the libc.so.6 from the machine that was compiled on, but we still give errors like this, and it seems dangerous anyways to have multiple versions of some STL files in use.

Delivering all the needed shared libraries together with the executable(s) is an alternative that may work -- and indeed may be required in conjunction with building for the earlier OS version instead of for the later, but it's not necessarily sufficient to just copy the shared library binaries from the build host. The executable and the libraries on which it depends, recursively, all need to be dynamically linked at runtime to the right versions of their needed libraries. It is not uncommon for these to be built in a way that does not provide for linking libraries from a non-standard path.

Another alternative is to perform all-static linking. This produces (much) larger executables, but they have no dependencies on the host system's libraries. Such binaries have a better chance of running on older versions of the target OS, though there are still potential issues with syscalls.

The most reliable alternative, at least for compiled software, is both build on the earliest OS you want to support and perform static linking.

If you are delivering a bunch of executables that use the same libraries, and you want to save space by using shared libraries, then it's still better to build on the earliest system you want to support, and package the result with the shared libraries for that OS version (which may involve tweaking or rebuilding some of the libs).

The problem was wsrep library /usr/lib/libgalera_smm.so is installed by default into different folder. Installation was ok, but the library is installed in

/usr/lib64/galera/libgalera_smm.so

Yh, it's completely fine.

To put it simply, MySQL is not MariaDB - as MariaDB is a Drop in replacement for MySQL.

MariaDB is a backward compatible, binary drop-in replacement of MySQL. What this means is:

• Data and table definition files (.frm) files are binary compatible.
• All client APIs, protocols and structs are identical.
• All filenames, binaries, paths, ports, sockets, and etc... should be the same.
• All MySQL connectors work unchanged with MariaDB.
• The mysql-client package also works with MariaDB server.

In most common practical scenarios, MariaDB version 5.x.y will work exactly like MySQL 5.x.y, MariaDB follows the version of MySQL, i.e. it's version number is used to indicate with which MySQL version it's compatible.

Edit 1: In apropos of comment

why this command does not work? sudo yum install mysql-server Loaded plugins: amazon-id, rhui-lb, search-disabled-repos No package mysql-server available.

By default MariaDB is supported - to install mysql-server you need to add it using RPM: