Replace the contents of the
storage/innobase directory in the MySQL
source tree with the InnoDB Plugin source tree.

Note

In MySQL 5.1.38 and up, the MySQL source tree also
contains a storage/innodb_plugin
directory, but that does not affect this procedure. The
source that you download from the InnoDB web site may
contain additional changes and fixes.

Compile and build MySQL. Instead of building a dynamic
InnoDB Plugin, it is advisable to build a version of
MySQL that contains the InnoDB Plugin. This is because
a dynamic InnoDB Plugin must be
built with exactly the same tools and options as the
mysqld executable, or spurious
errors may occur. Example:

Reconfigure the MySQL server by editing the
my.cnf option file to use InnoDB as the
default engine (if desired) and set appropriate
configuration parameters to enable use of new
InnoDB Plugin features, as described in section
Section 9.5, “Configuring the InnoDB Plugin”.
In particular, we recommend that you set the following
specific parameters as follows:

If you build a version of MySQL that contains the
InnoDB Plugin
(--with-plugins=innobase), you do not
have to tell MySQL to specify ignore_builtin_innodb or
specify plugin-load, or issue any INSTALL
PLUGIN statements. The mysqld
executable that you compiled will contain the new
InnoDB Plugin features.

Note: To fully exploit the performance improvements discussed in
Section 7.2, “Faster Locking for Improved Scalability”, the
InnoDB Plugin source code and build process makes some
compile-time tests of platform capabilities to automatically use
instructions for atomic memory access where available. If this
logic fails, you may need to contact MySQL support.