Comments - Build Environment Setup for Linux

CentOS 7 still comes with MariaDB 5.5 by default, so

yum-builddep mariadb

does not install dependencies that were added in MariaDB 10.x.

Also, for some strange reason, gcc, gcc-c++ and bison don't seem to be listed as build dependencies in the MariaDB 5.5 source package provided by CentOS.

So as a minimum in addition to the builddep step above

yum install gcc gcc-c++ libaio-devel

are also needed, and even a few more to actually build CentOS packages with the same feature set as the official MariaDB RPMs.

(unfortunately setting up MariaDB.(com|org) repositories for 10.x doesn't help either as build dependencies are fetched from RPM source packages which are not provided by MariaDB repositories yet, see https://jira.mariadb.org/browse/MDEV-7066 )

For an ARM processor on the Cubietruck 3.0, I did following steps to compile the software. Feel free to try this:

I did "rm CMakeCache.txt" because I forgot to install some dependencies and the cmake stops every time. Cleaning the cache is the only solution.

Also, this doesn't work on the internal NANDA flashdisk. You have to install an external hard disk on the cubietruck, because 2GByte is not enough for this program and all temporary data.

Between the steps, you can relax some hours, because ARM is not compiling too fast...

Now the software compiles, I wonder how to start it??? :-) For mysql, it asks a password and username.. but during this installation nothing is asked and there is no service started.

HI! Is there any way to compile mariadb with galera (10.1) on ARM? or alternate way to install 10.0 + galera?

Thanks

For MariaDB 5.5, you also need libaio-dev (since this is also a requirement for MySQL 5.5). Can someone verify this independently from me, then update the documentation? Thanks

I just tried building MariaDB 5.5 on a machine without libaio-dev installed and was successful. So as far as I can tell, it's not required.

The build process for 5.5 is very different than previous versions of MariaDB, so the documentation does need to be updated anyway, or at least a 5.5 build instructions page added.

When doing a source checkout, you are basically getting HEAD. How does one pick specific versions/tags?

Something like this should work:

bzr branch -rtag:${tagname} ${sourcedir} ${destname}

Example:

I have my MariaDB 5.2 tree in a folder called "5.2". To branch a MariaDB 5.2.9 tree I would do:

bzr branch -rtag:mariadb-5.2.9 5.2 mariadb-5.2.9

After it finishes the branch process I will have a "mariadb-5.2.9" folder with every commit up-to-and-including the one tagged "mariadb-5.2.9".