2.3 Installing a MySQL Source Distribution

Before you proceed with the source installation, check first to see if our binary is available for your platform and if it will work for you. We put a lot of effort into making sure that our binaries are built with the best possible options.

You need the following tools to build and install MySQL from source:

• GNU gunzip to uncompress the distribution.
• A reasonable tar to unpack the distribution. GNU tar is known to work. Some tar implementations that come pre-installed with the operating system (e.g. Sun tar) are known to have problems (with long file names, for example). In that case, you should install GNU tar first.
• A working ANSI C++ compiler. gcc >= 2.95.2, egcs >= 1.0.2 or egcs 2.91.66, SGI C++, and SunPro C++ are some of the compilers that are known to work. libg++ is not needed when using gcc. gcc 2.7.x has a bug that makes it impossible to compile some perfectly legal C++ files, such as `sql/sql_base.cc'. If you only have gcc 2.7.x, you must upgrade your gcc to be able to compile MySQL. gcc 2.8.1 is also known to have problems on some platforms, so it should be avoided if a new compiler exists for the platform. gcc >= 2.95.2 is recommended when compiling MySQL Version 3.23.x.
• A good make program. GNU make is always recommended and is sometimes required. If you have problems, we recommend trying GNU make 3.75 or newer.

If you are using a recent version of gcc, recent enough to understand the -fno-exceptions option, it is very important that you use it. Otherwise, you may compile a binary that crashes randomly. We also recommend that you use -felide-constructors and -fno-rtti along with -fno-exceptions. When in doubt, do the following:

CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions \
       -fno-rtti" ./configure --prefix=/usr/local/mysql --enable-assembler \
       --with-mysqld-ldflags=-all-static

On most systems this will give you a fast and stable binary.

If you run into problems, please always use mysqlbug when posting questions to mysql@lists.mysql.com. Even if the problem isn't a bug, mysqlbug gathers system information that will help others solve your problem. By not using mysqlbug, you lessen the likelihood of getting a solution to your problem. You will find mysqlbug in the `scripts' directory after you unpack the distribution. See section 1.7.1.3 How to Report Bugs or Problems.

Subsections

• 2.3.1 Quick Installation Overview
• 2.3.2 Applying Patches
• 2.3.3 Typical configure Options
• 2.3.4 Installing from the Development Source Tree
• 2.3.5 Problems Compiling MySQL?
• 2.3.6 MIT-pthreads Notes
• 2.3.7 Windows Source Distribution

User Comments

If you have problems compiling on an Athlon (gcc segfaulting), try changing to the directory enclosing the problem file, compiling the file with no optimization (i.e. removing -O2 and/or -O3). Then change back to the base directory and run make again. Worked for me!

Alternatively, turn optimization off for the entire build using -O0

--enable-assembler on OpenBSD 3.2 causeed errors in the make process. Took it out, worked okay. Not sure of the effects on performance yet, as I have not run 4.0 long enough yet. Hopefully it will be better than 3.23, because it crashed while outputting large ammounts of records often.

Add your own comment.