Comments - Knowledge Base Questions

From my perspective there should be build instructions specific to each file listed. MariaDB appears to be be working fine on my CentOS but we could make the source build much easier by taking the current MySQL instructions and finding a few items I needed:

Boost and the right version of cmake and ncurses-devel. yum helped a lot but the mysql_install_db script could be a bit more robust

One thing that caught me off gaurd was the choice of data directory

There should be an extra step before running mysql_install_db script because that script must know where the data directory will be placed in order to properly set up the database files

Turns out when --prefix=/usr/local/mysql the data directory defaults to /usr/local/mysql/var

It would have helped a lot to know this since if the folder is owned by mysql the data dir can be created without error ready to go. Again if the mysql_install_db script was more interactive it could have saved a headache there If anyone gets :

120211 18:39:05 mysqld_safe mysqld from pid file /usr/local/mysql/var/li394-220.pid ended
120211 18:39:25 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
120211 18:39:26 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
120211 18:39:26 [ERROR] /usr/local/mysql/libexec/mysqld: unknown variable 'debug=3'
120211 18:39:26 [ERROR] Aborting

The solution is to verify the log indicted data directory. Once you know that you should chown -R mysql and chgrp mysql that folder and then re-run mysql_install_db script Then re-try mysqld_safe as per mysql instructions

I also recommend redirecting stdout/stderr to log happenings e.g cmake . 1>/tmp/cmake_out.log 2>/tmp/cmake_err.log