Before you proceed with an installation from source, check whether
Oracle produces a precompiled binary distribution for your platform
and whether it works for you. We put a great deal of effort into
ensuring that our binaries are built with the best possible options
for optimal performance. Instructions for installing binary
distributions are available in
Chapter 3, Installing MySQL on Unix/Linux Using Generic Binaries.

Warning

Building MySQL with nonstandard options may lead to reduced
functionality, performance, or security.

Standard distributions are available as compressed
tar files, Zip archives, or RPM packages.
Distribution files have names of the form
mysql-VERSION.tar.gz,
mysql-VERSION.zip,
or
mysql-VERSION.rpm,
where VERSION is a number like
5.7.22. File names for source
distributions can be distinguished from those for precompiled
binary distributions in that source distribution names are
generic and include no platform name, whereas binary
distribution names include a platform name indicating the type
of system for which the distribution is intended (for example,
pc-linux-i686 or winx64).

Source Installation System Requirements

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/.

The Boost C++ libraries are required to build MySQL (but not to
use it). Boost 1.59.0 must be installed. To obtain Boost and its
installation instructions, visit
the official site.
After Boost is installed, tell the build system where the Boost
files are located by defining the
WITH_BOOST option when you invoke
CMake. For example:

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.