MySQL 5.6 Reference Manual Including MySQL NDB Cluster 7.3-7.4 Reference Guide
Installation of MySQL from source requires several development tools. Some of these tools are needed no matter whether you use a standard source distribution or a development source tree. Other tool requirements depend on which installation method you use.
To install MySQL from source, the following system requirements must be satisfied, regardless of installation method:
CMake, which is used as the build framework on all platforms. CMake can be downloaded from http://www.cmake.org.
A good make program. Although some platforms come with their own make implementations, it is highly recommended that you use GNU make 3.75 or higher. It may already be available on your system as gmake. GNU make is available from http://www.gnu.org/software/make/.
A working ANSI C++ compiler. GCC 4.2.1 or later, Sun Studio 12 or later, Visual Studio 2010 or later, and many current vendor-supplied compilers are known to work.
An SSL library is required for support of encrypted
connections, entropy for random number generation, and other
encryption-related operations. To specify the library
explicitly, use the WITH_SSL
option when you invoke CMake. For
additional information, see
Section 2.9.6, “Configuring SSL Library Support”.
The ncurses library.
Sufficient free memory. If you encounter problems such as “internal compiler error” when compiling large source files, it may be that you have too little memory. If compiling on a virtual machine, try increasing the memory allocation.
Perl is needed if you intend to run test scripts. Most Unix-like systems include Perl. On Windows, you can use a version such as ActiveState Perl.
To install MySQL from a standard source distribution, one of the following tools is required to unpack the distribution file:
For a .tar.gz
compressed
tar file: GNU gunzip
to
uncompress the distribution and a reasonable
tar to unpack it. If your
tar program supports the
z
option, it can both uncompress and unpack
the file.
GNU tar is known to work. The standard
tar provided with some operating systems is
not able to unpack the long file names in the MySQL
distribution. You should download and install GNU
tar, or if available, use a preinstalled
version of GNU tar. Usually this is available as
gnutar, gtar, or as
tar within a GNU or Free Software
directory, such as /usr/sfw/bin
or
/usr/local/bin
. GNU
tar is available from
http://www.gnu.org/software/tar/.
For a .zip
Zip archive:
WinZip or another tool that can read
.zip
files.
For an .rpm
RPM package: The
rpmbuild program used to build the
distribution unpacks it.
To install MySQL from a development source tree, the following additional tools are required:
The Git revision control system is required to obtain the development source code. The GitHub Help provides instructions for downloading and installing Git on different platforms. MySQL officially joined GitHub in September, 2014. For more information about MySQL's move to GitHub, refer to the announcement on the MySQL Release Engineering blog: MySQL on GitHub
bison 2.1 or higher, available from http://www.gnu.org/software/bison/. (Version 1 is no longer supported.) Use the latest version of bison where possible; if you experience problems, upgrade to a later version, rather than revert to an earlier one.
bison is available from
http://www.gnu.org/software/bison/.
bison
for Windows can be downloaded from
http://gnuwin32.sourceforge.net/packages/bison.htm.
Download the package labeled “Complete package,
excluding sources”. On Windows, the default location
for bison is the C:\Program
Files\GnuWin32
directory. Some utilities may fail
to find bison because of the space in the
directory name. Also, Visual Studio may simply hang if there
are spaces in the path. You can resolve these problems by
installing into a directory that does not contain a space (for
example C:\GnuWin32
).
On Solaris Express, m4 must be installed in addition to bison. m4 is available from http://www.gnu.org/software/m4/.
If you have to install any programs, modify your
PATH
environment variable to include any
directories in which the programs are located. See
Section 4.2.7, “Setting Environment Variables”.
If you run into problems and need to file a bug report, please use the instructions in Section 1.6, “How to Report Bugs or Problems”.