DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH
 

(mysql.info.gz) Installing source

Info Catalog (mysql.info.gz) Installing binary (mysql.info.gz) Installing (mysql.info.gz) Post-installation
 
 2.8 MySQL Installation Using a Source Distribution
 ==================================================
 
 Before you proceed with the source installation, check first to see
 whether our binary is available for your platform and whether it will
 work for you. We put a lot of effort into making sure that our binaries
 are built with the best possible options.
 
 To obtain a source distribution for MySQL,  Getting MySQL.
 
 MySQL source distributions are provided as compressed `tar' archives
 and have names of the form `mysql-VERSION.tar.gz', where VERSION is a
 number like `4.1.10a'.
 
 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 operating systems come with a pre-installed version
      of `tar' that is known to have problems.  For example, Mac OS X
      `tar' and Sun `tar' are known to have problems with long
      filenames.  On Mac OS X, you can use the pre-installed `gnutar'
      program.  On other systems with a deficient `tar', you should
      install GNU `tar' first.
 
    * A working ANSI C++ compiler.  `gcc' 2.95.2 or later, `egcs' 1.0.2
      or later 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 have only `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 or later is recommended when compiling MySQL 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 version of `gcc' recent enough to understand the
 `-fno-exceptions' option, it is _very important_ that you use this
 option. 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 a MySQL mailing list.  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.   Bug reports.
 

Menu

 
* Quick install               Source Installation Overview
* configure options           Typical `configure' Options
* Installing source tree      Installing from the Development Source Tree
* Compilation problems        Dealing with Problems Compiling MySQL
* MIT-pthreads                MIT-pthreads Notes
* Windows source build        Installing MySQL from Source on Windows
* Windows client compiling    Compiling MySQL Clients on Windows
 
Info Catalog (mysql.info.gz) Installing binary (mysql.info.gz) Installing (mysql.info.gz) Post-installation
automatically generated byinfo2html