Skip navigation links
Building MySQL from Source :: 3 Installing from the Development Source Tree
4 Dealing with Problems Compiling MySQL »
Section Navigation      [Toggle]

Chapter 3. Installing from the Development Source Tree

Caution

You should read this section only if you are interested in helping us test our new code. If you just want to get MySQL up and running on your system, you should use a standard release distribution (either a binary or source distribution).

To obtain the most recent development source tree, you must have Bazaar installed. You can obtain Bazaar from the Bazaar VCS Web site. Bazaar is supported by any platform that supports Python, and is therefore compatible with any Linux, Unix, Windows or Mac OS X host. Instructions for downloading and installing Bazaar on the different platforms are available on the Bazaar Web site.

All MySQL projects are hosted on Launchpad. MySQL projects, including MySQL server, MySQL Workbench, and others are available from the Sun/MySQL Engineering page. For the repositories related only to MySQL server, see the MySQL Server page.

To build under Unix/Linux, you must have the following tools installed:

To build under Windows you must have Microsoft Visual C++ 2005 Express Edition, Visual Studio .Net 2003 (7.1), or Visual Studio 2005 (8.0) compiler system.

Once the necessary tools are installed, you must create a local branch of the MySQL source code on your machine:

  1. To obtain a copy of the MySQL source code, you must create a new Bazaar branch. If you do not already have a Bazaar repository directory set up, you need to initialize a new directory: 

    shell> mkdir mysql-server
shell> bzr init-repo --trees mysql-server

  2. Once you have an initialized directory, you can branch from the public MySQL server repositories to create a local source tree. To create a branch of a specific version: 

    shell> cd mysql-server
shell> bzr branch lp:mysql-server/5.0 mysql-5.0

  3. The initial download will take some time to complete, depending on the speed of your connection. Please be patient. Once you have downloaded the first tree, additional trees should take significantly less time to download.

  4. When building from the Bazaar branch, you may want to create a copy of your active branch so that you can make configuration and other changes without affecting the original branch contents. You can achieve this by branching from the original branch: 

    shell> bzr branch mysql-5.0 mysql-5.0-build

  5. To obtain changes made after you have set up the branch initially, update it using the pull option periodically. Use this command in the top-level directory of the local copy: 

    shell> bzr pull

    You can examine the changeset comments for the tree by using the log option to bzr: 

    shell> bzr log

    You can also browse changesets, comments, and source code online. To browse this information for MySQL 5.0, go to the Launchpad MySQL Server page.

    If you see diffs (changes) or code that you have a question about, do not hesitate to send email to the MySQL internals mailing list. See MySQL Mailing Lists. Also, if you think you have a better idea on how to do something, send an email message to the list with a patch.

After you have the local branch, you can build MySQL server from the source code. On Windows, the build process is different from Unix/Linux: see Chapter 5, Installing MySQL from Source on Windows.

On Unix/Linux, use the autoconf system to create the configure script so that you can configure the build environment before building. The following example shows the typical commands required to build MySQL from a source tree.

  1. Change location to the top-level directory of the source tree; replace mysql-5.0 with the appropriate directory name. 

    shell> cd mysql-5.0

  2. Prepare the source tree for configuration.

    You must separately configure the BDB and InnoDB storage engines. Run the following commands from the main source directory: 

    shell> (cd bdb/dist; sh s_all)
shell> (cd innobase; autoreconf --force --install)

    You can omit the previous commands if you do not require BDB or InnoDB support.

    Prepare the remainder of the source tree: 

    shell> autoreconf --force --install

    As an alternative to the preceding autoreconf command, you can use BUILD/autorun.sh, which acts as a shortcut for the following sequence of commands: 

    shell> aclocal; autoheader
shell> libtoolize --automake --force
shell> automake --force --add-missing; autoconf
shell> (cd bdb/dist; sh s_all)
shell> (cd innobase; aclocal; autoheader; autoconf; automake)

    If you get some strange errors during this stage, verify that you have the correct version of libtool installed.

  3. Configure the source tree and compile MySQL: 

    shell> ./configure  # Add your favorite options here
shell> make

    For a description of some configure options, see Chapter 2, Typical configure Options.

    A collection of our standard configuration scripts is located in the BUILD/ subdirectory. For example, you may find it more convenient to use the BUILD/compile-pentium-debug script than the preceding set of shell commands. To compile on a different architecture, modify the script by removing flags that are Pentium-specific, or use another script that may be more appropriate. These scripts are provided on an “as-is” basis. They are not officially maintained and their contents may change from release to release.

  4. When the build is done, run make install. Be careful with this on a production machine; the command may overwrite your live release installation. If you already have MySQL installed and do not want to overwrite it, run ./configure with values for the --prefix, --with-tcp-port, and --with-unix-socket-path options different from those used for your production server.

  5. Play hard with your new installation and try to make the new features crash. Start by running make test. See MySQL Test Suite.

  6. If you have gotten to the make stage, but the distribution does not compile, please enter the problem into our bugs database using the instructions given in How to Report Bugs or Problems. If you have installed the latest versions of the required GNU tools, and they crash trying to process our configuration files, please report that also. However, if you get a command not found error or a similar problem for aclocal, configure, or other required tools, do not report it. Instead, make sure that all the required tools are installed and that your PATH variable is set correctly so that your shell can find them.