The Ultimate Guide to High Availability with MariaDB

CMAKE settings to include TokuDB in 5.5.34

I am trying to build 5.5.34 from source on Linux x64 (Fedora 14).

I was looking at the readme files and could not find anything about building 5.5.34 from source and including TokuDB (which has the source code in the /storage/TokuDB/ directory) into the build.

I was looking for something like: -DWITH_TOKUDB_STORAGE_ENGINE=ON but did not stumble across anything.

Anybody got some ideas?

Here is my build script:

rm -f CMakeCache.txt

make clean

cmake \ -DCMAKE_BUILD_TYPE=Release \ -DCMAKE_INSTALL_PREFIX=/mysql \ -DENABLED_PROFILING=OFF \ -DENABLE_DEBUG_SYNC=ON \ -DENABLE_GCOV=OFF \ -DINSTALL_LAYOUT=STANDALONE \ -DMYSQL_DATADIR=/mysql/data \ -DINSTALL_INCLUDEDIR=include/mysql \ -DINSTALL_UNIX_ADDRDIR=/mysql/mysql.sock \ -DUSE_ARIA_FOR_TMP_TABLES=ON \ -DWITHOUT_PBXT_STORAGE_ENGINE=ON \ -DWITHOUT_SERVER=OFF \ -DWITH_ARCHIVE_STORAGE_ENGINE=OFF \ -DWITH_EMBEDDED_SERVER=OFF \ -DWITH_FAST_MUTEXES=OFF \ -DWITH_FEDERATEDX_STORAGE_ENGINE=OFF \ -DWITH_FEEDBACK=OFF \ -DWITH_LIBWRAP=OFF \ -DWITH_PIC=ON \ -DWITH_PARTITION_STORAGE_ENGINE=OFF \ -DWITH_PERFSCHEMA_STORAGE_ENGINE=ON \ -DWITH_SPHINX_STORAGE_ENGINE=OFF \ -DWITH_SSL=OFF \ -DWITH_UNIT_TESTS=OFF \ -DWITH_VALGRIND=OFF \ -DWITH_XTRADB_STORAGE_ENGINE=ON \ -DWITHOUT_OQGRAPH=ON \ -DWITH_ZLIB=bundled

make

(now compiling your program)

Answer Answered by Sergei Golubchik in this comment.

normally all plugins are enabled by default. See specifying-what-plugins-to-build

But TokuDB has specific build requirements, make sure they're all met. You need gcc at least 4.7 and cmake at least 2.8.9

See the cmake output. If you'll see

-- Performing Test TOKUDB_OK

then TokuDB is enabled. And if you'll see

-- Performing Test TOKUDB_OK - Success

then all build prerequisites are met.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.