GNU Info

Info Node: (mysql.info)Installing source tree

(mysql.info)Installing source tree


Next: Compilation problems Prev: configure options Up: Installing source
Enter node , (file) or (file)node

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 source or binary distribution will do).

To obtain our most recent development source tree, use these
instructions:

  1. Download *BitKeeper* from
     `http://www.bitmover.com/cgi-bin/download.cgi'.  You will need
     *Bitkeeper* 2.0 or newer to access our repository.

  2. Follow the instructions to install it.

  3. After *BitKeeper* is installed, use this command if you want to
     clone the MySQL 3.23 branch:

          shell> bk clone bk://work.mysql.com:7000 mysql

     To clone the 4.0 branch, use this command instead:

          shell> bk clone bk://work.mysql.com:7001 mysql-4.0

     The initial download of the source tree may take a while,
     depending on the speed of your connection; be patient.

  4. You will need GNU `autoconf', `automake', `libtool', and `m4' to
     run the next set of commands.  If you get some strange error
     during this stage, check that you really have `libtool' installed!

          shell> cd mysql
          shell> bk -r edit
          shell> aclocal; autoheader; autoconf;  automake;
          shell> ./configure  # Add your favorite options here
          shell> make

     A collection of our standard configure scripts is located in the
     `BUILD/' subdirectory.  If you are lazy, you can use
     `BUILD/compile-pentium-debug'. To compile on a different
     architecture, modify the script removing flags that are
     Pentium-specific.

  5. 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 have another installation of MySQL,
     we recommand that you run `./configure' with different values for
     the `prefix', `tcp-port', and `unix-socket-path' options than
     those used for your production server.

  6. Play hard with your new installation and try to make the new
     features crash.  Start by running `make test'.  Note: MySQL test
     suite.

  7. If you have gotten to the `make' stage and the distribution does
     not compile, please report it to <bugs@lists.mysql.com>.  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 execute `aclocal' and get a
     `command not found' error or a similar problem, do not report it.
     Instead, make sure all the necessary tools are installed and that
     your `PATH' variable is set correctly so your shell can find them.

  8. After the initial `bk clone' operation to get the source tree, you
     should run `bk pull' periodically to get the updates.

  9. You can examine the change history for the tree with all the diffs
     by using `bk sccstool'.  If you see some funny diffs or code that
     you have a question about, do not hesitate to send e-mail to
     <internals@lists.mysql.com>.  Also, if you think you have a better
     idea on how to do something, send an email to the same address
     with a patch.  `bk diffs' will produce a patch for you after you
     have made changes to the source. If you do not have the time to
     code your idea, just send a description.

 10. *BitKeeper* has a nice help utility that you can access via `bk
     helptool'.



automatically generated by info2www version 1.2.2.9