From: Date: June 20 2007 10:53pm Subject: svn commit - mysqldoc@docsrva: r6874 - trunk/refman-5.1 List-Archive: http://lists.mysql.com/commits/29221 Message-Id: <200706202053.l5KKr1LZ015758@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: jstephens Date: 2007-06-20 22:53:01 +0200 (Wed, 20 Jun 2007) New Revision: 6874 Log: More of the telco build script (includes corrections needed for change of some options and script name). Modified: trunk/refman-5.1/mysql-cluster-cge-building-tmp.xml Modified: trunk/refman-5.1/mysql-cluster-cge-building-tmp.xml =================================================================== --- trunk/refman-5.1/mysql-cluster-cge-building-tmp.xml 2007-06-20 17:48:54 UTC (rev 6873) +++ trunk/refman-5.1/mysql-cluster-cge-building-tmp.xml 2007-06-20 20:53:01 UTC (rev 6874) Changed blocks: 11, Lines Added: 207, Lines Deleted: 19; 10149 bytes @@ -12,7 +12,7 @@ This section provides instructions on building &mccge-series; using the source code that can be obtained from the MySQL FTP site and the - build_source.sh script that can be found in the + build_mccge.sh script that can be found in the source code's BUILD directory. @@ -21,7 +21,7 @@ MCCGE Build Script Usage — Basics - The build_source.sh script is intended to + The build_mccge.sh script is intended to provide an easy way to build &mccge-series; binaries on the principal supported platforms for this product: @@ -80,7 +80,7 @@ shell> cd mccge-root -shell> BUILD/build_source.sh +shell> BUILD/build_mccge.sh This script must be invoked from the root @@ -91,7 +91,7 @@ shell> cd mccge-root/BUILD -shell> ./build_source.sh +shell> ./build_mccge.sh You must run this script from the MySQL top-level directory @@ -112,7 +112,7 @@ To build on other platforms you can use the - option on a supported platform and + option on a supported platform and edit the output for the proper set of commands for the specific platform you are using. MySQL can also provide custom CGE builds for any type of platform that is officially supported for MySQL @@ -128,7 +128,7 @@ Using the option with - build_source.sh, it is possible to build a + build_mccge.sh, it is possible to build a number of different packages. These include a Classic version of MySQL having only the MyISAM storage engine, a Pro @@ -298,7 +298,7 @@ options used for all packages (see , for information on available packages), and whether the default can be - overridden when using build_source.sh: + overridden when using build_mccge.sh: @@ -610,13 +610,200 @@ +
+ + Compiler Options Used by <command>build_mccge.sh</command> + + + This section describes the compiler options used for each of the + different platforms supported by this script. + + + + The option adds + to the C/C++ flags (provides + support for Nocona, K8, and other processors). + + + + Use of the --debug option adds -g to the C/C++ flags. + + + + + Linux/x86 using <command>gcc</command> + + + No default compiler flags are used. Instead the configure script + determines the proper flags to use for both normal and debug + builds. Discovery of a Nocona or Core 2 Duo CPU causes a 64-bit + binary to be built; otherwise, the binary is 32-bit. To build a + 64-bit binary, is added to the C/C++ + flags. + + + + To build a 32-bit binary on a 64-bit CPU, use the + option as described in + . + + + + + + + + + Linux/x86 using <command>icc</command> + + + Flags used: + + + + + + CC: + + + + + + C++: + + + + + + C and C++: + + + + + + The normal and fast versions also add the following C and C++ + flags: . + + + + + + On discovery of a Core 2 Duo architecture while using + icc, is also added to the + C/C++ flags; this provides optimisations specific to Core 2 Duo. + + + + + Solaris/x86 using <command>gcc</command> + + + All builds on Solaris are 64-bit, so is + always used in the C/C++ flags. LDFLAGS is + set to . Solaris + builds also set . + + + + + + + Solaris/Sparc using <command>Forte</command> + + + On this platform, cc-5.0 is used as + CC, and sets + , so that Sparc v9 + binaries are compiled using the following flags: + + + + + + C flags: + + + + + + C++ flags: + + + + + + C/C++ flags: + + + + + + For normal builds, the following flags are also used: + + + + + + C flags: + + + + + + C/C++ flags: + + + + + + As on Solaris/x86, Solaris/Sparc builds set + . + + + + + + + MacOSX/x86 using <command>gcc</command> + + + C and C++ flags include . + Non-debug versions also add , where means + the build is space-optimized as long as the space optimizations + do not negatively affect performance. Debug versions use + . + + + + + + + Additional compiler options + + + To obtain extended help on the + options + available, run this script with + to create a configuration + file. Then issue the command ./configure + to get an extended list of + possible configure options. + + + + +
+
Build Script Options Quick Reference The following table provides a quick reference for options - available for use with build_source.sh. + available for use with build_mccge.sh. @@ -643,8 +830,13 @@ Select compiler + + + Stop after running configure. + + + [none] - Build with data directory set to non-standard path @@ -686,16 +878,6 @@ table. - - - Stop after running configure. - - - - [none] - Print commands that the script will execute, but do not execute - - [none] Use GPL libraries @@ -726,6 +908,12 @@ Build with prefix path + + [none] + Print commands that the script would execute, but do not actually + execute them. + + [none] Statically link system libraries into binaries