List:Commits« Previous MessageNext Message »
From:paul.dubois Date:November 16 2010 8:03pm
Subject:svn commit - mysqldoc@docsrva: r23788 - in trunk: . refman-5.1 refman-5.5 refman-5.6
View as plain text  
Author: paul
Date: 2010-11-16 21:03:31 +0100 (Tue, 16 Nov 2010)
New Revision: 23788

Log:
 r65616@frost:  paul | 2010-11-16 14:00:13 -0500
 Move sections


Modified:
   trunk/refman-5.1/installing-aix.xml
   trunk/refman-5.1/installing-hpux.xml
   trunk/refman-5.1/installing-solaris.xml
   trunk/refman-5.1/installing-source-core.xml
   trunk/refman-5.5/installing-aix.xml
   trunk/refman-5.5/installing-hpux.xml
   trunk/refman-5.5/installing-solaris.xml
   trunk/refman-5.5/installing-source-core.xml
   trunk/refman-5.6/installing-aix.xml
   trunk/refman-5.6/installing-hpux.xml
   trunk/refman-5.6/installing-solaris.xml
   trunk/refman-5.6/installing-source-core.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:44270
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:65615
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
   + 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:44270
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:65616
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546


Modified: trunk/refman-5.1/installing-aix.xml
===================================================================
--- trunk/refman-5.1/installing-aix.xml	2010-11-16 20:03:22 UTC (rev 23787)
+++ trunk/refman-5.1/installing-aix.xml	2010-11-16 20:03:31 UTC (rev 23788)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 101; 3609 bytes

@@ -69,105 +69,4 @@
 
   </section>
 
-  <section id="aix-installation-source">
-
-    <title>Notes on Installing MySQL on AIX from Source</title>
-
-    <para>
-      General notes on building MySQL from source on IBM AIX:
-    </para>
-
-    <itemizedlist>
-
-      <listitem>
-        <para>
-          Automatic detection of <literal>xlC</literal> is missing from
-          Autoconf, so a number of variables need to be set before
-          running <command>configure</command>. The following example
-          uses the IBM compiler:
-        </para>
-
-<programlisting>
-export CC="xlc_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192 "
-export CXX="xlC_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192"
-export CFLAGS="-I /usr/local/include"
-export LDFLAGS="-L /usr/local/lib"
-export CPPFLAGS=$CFLAGS
-export CXXFLAGS=$CFLAGS
-
-./configure --prefix=/usr/local \
-                --localstatedir=/var/mysql \
-                --sbindir='/usr/local/bin' \
-                --libexecdir='/usr/local/bin' \
-                --enable-thread-safe-client \
-                --enable-large-files
-</programlisting>
-
-        <para>
-          The preceding options are used to compile the MySQL
-          distribution that can be found at
-          <ulink url="http://www-frec.bull.com/"/>.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you change the <option>-O3</option> to <option>-O2</option>
-          in the preceding <command>configure</command> line, you must
-          also remove the <option>-qstrict</option> option. This is a
-          limitation in the IBM C compiler.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you are using <command>gcc</command> to compile MySQL, you
-          <emphasis>must</emphasis> use the
-          <option>-fno-exceptions</option> flag, because the exception
-          handling in <command>gcc</command> is not thread-safe. There
-          are also some known problems with IBM's assembler that may
-          cause it to generate bad code when used with
-          <command>gcc</command>.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you have problems with signals (MySQL dies unexpectedly
-          under high load), you may have found an OS bug with threads
-          and signals. In this case, you can tell MySQL not to use
-          signals by configuring as follows:
-        </para>
-
-<programlisting>
-CFLAGS=-DDONT_USE_THR_ALARM CXX=gcc \
-CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti \
--DDONT_USE_THR_ALARM" \
-./configure --prefix=/usr/local/mysql --with-debug \
-    --with-low-memory
-</programlisting>
-
-        <para>
-          This does not affect the performance of MySQL, but has the
-          side effect that you cannot kill clients that are
-          <quote>sleeping</quote> on a connection with
-          <command>mysqladmin kill</command> or <command>mysqladmin
-          shutdown</command>. Instead, the client dies when it issues
-          its next command.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          On some versions of AIX, linking with
-          <literal>libbind.a</literal> makes
-          <literal>getservbyname()</literal> dump core. This is an AIX
-          bug and should be reported to IBM.
-        </para>
-      </listitem>
-
-    </itemizedlist>
-
-  </section>
-
 </section>


Modified: trunk/refman-5.1/installing-hpux.xml
===================================================================
--- trunk/refman-5.1/installing-hpux.xml	2010-11-16 20:03:22 UTC (rev 23787)
+++ trunk/refman-5.1/installing-hpux.xml	2010-11-16 20:03:31 UTC (rev 23788)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 59; 1925 bytes

@@ -104,65 +104,6 @@
 
   </section>
 
-  <section id="hpux-installation-source">
-
-    <title>Notes on Installing MySQL on HP-UX from Source</title>
-
-    <para>
-      Additional notes on compiling MySQL on HP-UX.
-    </para>
-
-    <itemizedlist>
-
-      <listitem>
-        <para>
-          If you are using HP-UX compiler, you can use the following
-          command (which has been tested with <command>cc</command>
-          B.11.11.04):
-        </para>
-
-<programlisting>
-CC=cc CXX=aCC CFLAGS=+DD64 CXXFLAGS=+DD64 ./configure \
-    --with-extra-character-set=complex
-</programlisting>
-
-        <para>
-          You can ignore any errors of the following type:
-        </para>
-
-<programlisting>
-aCC: warning 901: unknown option: `-3': use +help for online
-documentation
-</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you get the following error from
-          <command>configure</command>, verify that you do not have the
-          path to the K&amp;R compiler before the path to the HP-UX C
-          and C++ compiler:
-        </para>
-
-<programlisting>
-checking for cc option to accept ANSI C... no
-configure: error: MySQL requires an ANSI C compiler (and a C++ compiler).
-Try gcc. See the Installation chapter in the Reference Manual.
-</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Another reason for not being able to compile is that you did
-          not define the <literal>+DD64</literal> flags as just
-          described.
-        </para>
-      </listitem>
-
-    </itemizedlist>
-
-  </section>
-
   <section id="hpux-installation-depot">
 
     <title>Installing MySQL on HP-UX using DEPOT</title>


Modified: trunk/refman-5.1/installing-solaris.xml
===================================================================
--- trunk/refman-5.1/installing-solaris.xml	2010-11-16 20:03:22 UTC (rev 23787)
+++ trunk/refman-5.1/installing-solaris.xml	2010-11-16 20:03:31 UTC (rev 23788)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 239; 7990 bytes

@@ -411,243 +411,4 @@
 
   </section>
 
-  <section id="solaris-installation-source">
-
-    <title>Notes on Installing MySQL on Solaris from Source</title>
-
-    <para>
-      When building MySQL on Solaris you can use either the Sun Studio
-      or GNU cc compilers. For more information on specific notes and
-      environments, use the following hints.
-    </para>
-
-    <itemizedlist>
-
-      <listitem>
-        <para>
-          When building you should ensure that your
-          <literal>PATH</literal> variable includes the necessary tools,
-          including <command>ar</command> for building libraries. Some
-          tools are located in <filename>/usr/ccs/bin</filename>.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          When running <command>configure</command>, you should specify
-          the C and C++ compiler explicitly to ensure that the right C
-          compiler combination is used:
-        </para>
-
-<programlisting>$ configure CC=gcc CXX=g++</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          For detailed information on performance tuning your MySQL
-          installation for Solaris, you can use the information from
-          <ulink url="http://blogs.sun.com/krishs/entry/sun_studio_compiler_options_for">Krish
-          Shankar</ulink> and the
-          <ulink url="http://developers.sun.com/solaris/articles/mysql_perf_tune.html">Sun
-          Solaris MySQL Performance Tuning</ulink> pages.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you have an UltraSPARC system, you can get 4% better
-          performance by adding <option>-mcpu=v8
-          -Wa,-xarch=v8plusa</option> to the <literal>CFLAGS</literal>
-          and <literal>CXXFLAGS</literal> environment variables.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you have Sun's Forte 5.00 (or newer) or Sun Studio
-          compiler, you can run <command>configure</command> like this:
-        </para>
-
-<programlisting>
-CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt" \
-CXX=CC CXXFLAGS="-noex -mt" \
-./configure --prefix=/usr/local/mysql --enable-assembler
-</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          To create a 64-bit SPARC binary with Sun's Forte or Sun Studio
-          compiler, use the following configuration options:
-        </para>
-
-<programlisting>
-CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt -xarch=v9" \
-CXX=CC CXXFLAGS="-noex -mt -xarch=v9" ASFLAGS="-xarch=v9" \
-./configure --prefix=/usr/local/mysql --enable-assembler
-</programlisting>
-
-        <para>
-          To create a 64-bit Solaris binary using
-          <command>gcc</command>, add <option>-m64</option> to
-          <literal>CFLAGS</literal> and <literal>CXXFLAGS</literal> and
-          remove <option>--enable-assembler</option> from the
-          <command>configure</command> line.
-        </para>
-
-        <para>
-          In the MySQL benchmarks, we obtained a 4% speed increase on
-          UltraSPARC when using Forte 5.0 in 32-bit mode, as compared to
-          using <command>gcc</command> 3.2 with the
-          <option>-mcpu</option> flag.
-        </para>
-
-        <para>
-          If you create a 64-bit <command>mysqld</command> binary, it is
-          4% slower than the 32-bit binary, but can handle more threads
-          and memory.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you get a problem with <literal>fdatasync</literal> or
-          <literal>sched_yield</literal>, you can fix this by adding
-          <literal>LIBS=-lrt</literal> to the
-          <command>configure</command> line
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          Solaris does not provide static versions of all system
-          libraries (<literal>libpthreads</literal> and
-          <literal>libdl</literal>), so you cannot compile MySQL with
-          <option>--static</option>. If you try to do so, you get one of
-          the following errors:
-        </para>
-
-<programlisting>
-ld: fatal: library -ldl: not found
-undefined reference to `dlopen'
-cannot find -lrt
-</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you link your own MySQL client programs, you may see the
-          following error at runtime:
-        </para>
-
-<programlisting>
-ld.so.1: fatal: libmysqlclient.so.#:
-open failed: No such file or directory
-</programlisting>
-
-        <para>
-          This problem can be avoided by one of the following methods:
-        </para>
-
-        <itemizedlist>
-
-          <listitem>
-            <para>
-              Use the <literal>crle</literal> tool to add the directory
-              containing the <literal>libmysqlclient</literal> library
-              file to the list of standard library directories. You need
-              administrator privileges to do this. Make sure you update
-              the library information, rather than replace it with the
-              new path. For example, the following command adds the
-              directory to the list of standard directories searched for
-              libraries.
-            </para>
-
-<programlisting>shell&gt; crle -u -l /usr/local/mysql/lib</programlisting>
-
-            <para>
-              For 64-bit libraries, add the <literal>-64</literal>
-              option:
-            </para>
-
-<programlisting>shell&gt; crle -64 -u -l /usr/local/mysql/lib</programlisting>
-          </listitem>
-
-          <listitem>
-            <para>
-              Link clients with the
-              <option>-Wl,r/full/path/to/libmysqlclient.so</option> flag
-              rather than with <option>-Lpath</option>).
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
-              Copy <literal>libmysqclient.so</literal> to
-              <filename>/usr/lib</filename>.
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
-              <indexterm>
-                <primary>LD_RUN_PATH environment variable</primary>
-              </indexterm>
-
-              <indexterm>
-                <primary>environment variable</primary>
-                <secondary>LD_RUN_PATH</secondary>
-              </indexterm>
-
-              Add the path name of the directory where
-              <filename>libmysqlclient.so</filename> is located to the
-              <literal>LD_RUN_PATH</literal> environment variable before
-              running your client.
-            </para>
-          </listitem>
-
-        </itemizedlist>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you have problems with <command>configure</command> trying
-          to link with <option>-lz</option> when you do not have
-          <literal>zlib</literal> installed, you have two options:
-        </para>
-
-        <itemizedlist>
-
-          <listitem>
-            <para>
-              If you want to be able to use the compressed communication
-              protocol, you need to get and install
-              <literal>zlib</literal> from
-              <literal>ftp.gnu.org</literal>.
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
-              Run <command>configure</command> with the
-              <option>--with-named-z-libs=no</option> option when
-              building MySQL.
-            </para>
-          </listitem>
-
-        </itemizedlist>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you are using <command>gcc</command> and have problems with
-          loading user-defined functions (UDFs) into MySQL, try adding
-          <option>-lgcc</option> to the link line for the UDF.
-        </para>
-      </listitem>
-
-    </itemizedlist>
-
-  </section>
-
 </section>


Modified: trunk/refman-5.1/installing-source-core.xml
===================================================================
--- trunk/refman-5.1/installing-source-core.xml	2010-11-16 20:03:22 UTC (rev 23787)
+++ trunk/refman-5.1/installing-source-core.xml	2010-11-16 20:03:31 UTC (rev 23788)
Changed blocks: 1, Lines Added: 399, Lines Deleted: 0; 12832 bytes

@@ -3143,4 +3143,403 @@
 
   </section>
 
+  <section id="solaris-installation-source">
+
+    <title>Notes on Installing MySQL on Solaris from Source</title>
+
+    <para>
+      When building MySQL on Solaris you can use either the Sun Studio
+      or GNU cc compilers. For more information on specific notes and
+      environments, use the following hints.
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          When building you should ensure that your
+          <literal>PATH</literal> variable includes the necessary tools,
+          including <command>ar</command> for building libraries. Some
+          tools are located in <filename>/usr/ccs/bin</filename>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          When running <command>configure</command>, you should specify
+          the C and C++ compiler explicitly to ensure that the right C
+          compiler combination is used:
+        </para>
+
+<programlisting>$ configure CC=gcc CXX=g++</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          For detailed information on performance tuning your MySQL
+          installation for Solaris, you can use the information from
+          <ulink url="http://blogs.sun.com/krishs/entry/sun_studio_compiler_options_for">Krish
+          Shankar</ulink> and the
+          <ulink url="http://developers.sun.com/solaris/articles/mysql_perf_tune.html">Sun
+          Solaris MySQL Performance Tuning</ulink> pages.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you have an UltraSPARC system, you can get 4% better
+          performance by adding <option>-mcpu=v8
+          -Wa,-xarch=v8plusa</option> to the <literal>CFLAGS</literal>
+          and <literal>CXXFLAGS</literal> environment variables.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you have Sun's Forte 5.00 (or newer) or Sun Studio
+          compiler, you can run <command>configure</command> like this:
+        </para>
+
+<programlisting>
+CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt" \
+CXX=CC CXXFLAGS="-noex -mt" \
+./configure --prefix=/usr/local/mysql --enable-assembler
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          To create a 64-bit SPARC binary with Sun's Forte or Sun Studio
+          compiler, use the following configuration options:
+        </para>
+
+<programlisting>
+CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt -xarch=v9" \
+CXX=CC CXXFLAGS="-noex -mt -xarch=v9" ASFLAGS="-xarch=v9" \
+./configure --prefix=/usr/local/mysql --enable-assembler
+</programlisting>
+
+        <para>
+          To create a 64-bit Solaris binary using
+          <command>gcc</command>, add <option>-m64</option> to
+          <literal>CFLAGS</literal> and <literal>CXXFLAGS</literal> and
+          remove <option>--enable-assembler</option> from the
+          <command>configure</command> line.
+        </para>
+
+        <para>
+          In the MySQL benchmarks, we obtained a 4% speed increase on
+          UltraSPARC when using Forte 5.0 in 32-bit mode, as compared to
+          using <command>gcc</command> 3.2 with the
+          <option>-mcpu</option> flag.
+        </para>
+
+        <para>
+          If you create a 64-bit <command>mysqld</command> binary, it is
+          4% slower than the 32-bit binary, but can handle more threads
+          and memory.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you get a problem with <literal>fdatasync</literal> or
+          <literal>sched_yield</literal>, you can fix this by adding
+          <literal>LIBS=-lrt</literal> to the
+          <command>configure</command> line
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Solaris does not provide static versions of all system
+          libraries (<literal>libpthreads</literal> and
+          <literal>libdl</literal>), so you cannot compile MySQL with
+          <option>--static</option>. If you try to do so, you get one of
+          the following errors:
+        </para>
+
+<programlisting>
+ld: fatal: library -ldl: not found
+undefined reference to `dlopen'
+cannot find -lrt
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you link your own MySQL client programs, you may see the
+          following error at runtime:
+        </para>
+
+<programlisting>
+ld.so.1: fatal: libmysqlclient.so.#:
+open failed: No such file or directory
+</programlisting>
+
+        <para>
+          This problem can be avoided by one of the following methods:
+        </para>
+
+        <itemizedlist>
+
+          <listitem>
+            <para>
+              Use the <literal>crle</literal> tool to add the directory
+              containing the <literal>libmysqlclient</literal> library
+              file to the list of standard library directories. You need
+              administrator privileges to do this. Make sure you update
+              the library information, rather than replace it with the
+              new path. For example, the following command adds the
+              directory to the list of standard directories searched for
+              libraries.
+            </para>
+
+<programlisting>shell&gt; crle -u -l /usr/local/mysql/lib</programlisting>
+
+            <para>
+              For 64-bit libraries, add the <literal>-64</literal>
+              option:
+            </para>
+
+<programlisting>shell&gt; crle -64 -u -l /usr/local/mysql/lib</programlisting>
+          </listitem>
+
+          <listitem>
+            <para>
+              Link clients with the
+              <option>-Wl,r/full/path/to/libmysqlclient.so</option> flag
+              rather than with <option>-Lpath</option>).
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              Copy <literal>libmysqclient.so</literal> to
+              <filename>/usr/lib</filename>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <indexterm>
+                <primary>LD_RUN_PATH environment variable</primary>
+              </indexterm>
+
+              <indexterm>
+                <primary>environment variable</primary>
+                <secondary>LD_RUN_PATH</secondary>
+              </indexterm>
+
+              Add the path name of the directory where
+              <filename>libmysqlclient.so</filename> is located to the
+              <literal>LD_RUN_PATH</literal> environment variable before
+              running your client.
+            </para>
+          </listitem>
+
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you have problems with <command>configure</command> trying
+          to link with <option>-lz</option> when you do not have
+          <literal>zlib</literal> installed, you have two options:
+        </para>
+
+        <itemizedlist>
+
+          <listitem>
+            <para>
+              If you want to be able to use the compressed communication
+              protocol, you need to get and install
+              <literal>zlib</literal> from
+              <literal>ftp.gnu.org</literal>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              Run <command>configure</command> with the
+              <option>--with-named-z-libs=no</option> option when
+              building MySQL.
+            </para>
+          </listitem>
+
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you are using <command>gcc</command> and have problems with
+          loading user-defined functions (UDFs) into MySQL, try adding
+          <option>-lgcc</option> to the link line for the UDF.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
+  <section id="aix-installation-source">
+
+    <title>Notes on Installing MySQL on AIX from Source</title>
+
+    <para>
+      General notes on building MySQL from source on IBM AIX:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          Automatic detection of <literal>xlC</literal> is missing from
+          Autoconf, so a number of variables need to be set before
+          running <command>configure</command>. The following example
+          uses the IBM compiler:
+        </para>
+
+<programlisting>
+export CC="xlc_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192 "
+export CXX="xlC_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192"
+export CFLAGS="-I /usr/local/include"
+export LDFLAGS="-L /usr/local/lib"
+export CPPFLAGS=$CFLAGS
+export CXXFLAGS=$CFLAGS
+
+./configure --prefix=/usr/local \
+                --localstatedir=/var/mysql \
+                --sbindir='/usr/local/bin' \
+                --libexecdir='/usr/local/bin' \
+                --enable-thread-safe-client \
+                --enable-large-files
+</programlisting>
+
+        <para>
+          The preceding options are used to compile the MySQL
+          distribution that can be found at
+          <ulink url="http://www-frec.bull.com/"/>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you change the <option>-O3</option> to <option>-O2</option>
+          in the preceding <command>configure</command> line, you must
+          also remove the <option>-qstrict</option> option. This is a
+          limitation in the IBM C compiler.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you are using <command>gcc</command> to compile MySQL, you
+          <emphasis>must</emphasis> use the
+          <option>-fno-exceptions</option> flag, because the exception
+          handling in <command>gcc</command> is not thread-safe. There
+          are also some known problems with IBM's assembler that may
+          cause it to generate bad code when used with
+          <command>gcc</command>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you have problems with signals (MySQL dies unexpectedly
+          under high load), you may have found an OS bug with threads
+          and signals. In this case, you can tell MySQL not to use
+          signals by configuring as follows:
+        </para>
+
+<programlisting>
+CFLAGS=-DDONT_USE_THR_ALARM CXX=gcc \
+CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti \
+-DDONT_USE_THR_ALARM" \
+./configure --prefix=/usr/local/mysql --with-debug \
+    --with-low-memory
+</programlisting>
+
+        <para>
+          This does not affect the performance of MySQL, but has the
+          side effect that you cannot kill clients that are
+          <quote>sleeping</quote> on a connection with
+          <command>mysqladmin kill</command> or <command>mysqladmin
+          shutdown</command>. Instead, the client dies when it issues
+          its next command.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          On some versions of AIX, linking with
+          <literal>libbind.a</literal> makes
+          <literal>getservbyname()</literal> dump core. This is an AIX
+          bug and should be reported to IBM.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
+  <section id="hpux-installation-source">
+
+    <title>Notes on Installing MySQL on HP-UX from Source</title>
+
+    <para>
+      Additional notes on compiling MySQL on HP-UX.
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          If you are using HP-UX compiler, you can use the following
+          command (which has been tested with <command>cc</command>
+          B.11.11.04):
+        </para>
+
+<programlisting>
+CC=cc CXX=aCC CFLAGS=+DD64 CXXFLAGS=+DD64 ./configure \
+    --with-extra-character-set=complex
+</programlisting>
+
+        <para>
+          You can ignore any errors of the following type:
+        </para>
+
+<programlisting>
+aCC: warning 901: unknown option: `-3': use +help for online
+documentation
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you get the following error from
+          <command>configure</command>, verify that you do not have the
+          path to the K&amp;R compiler before the path to the HP-UX C
+          and C++ compiler:
+        </para>
+
+<programlisting>
+checking for cc option to accept ANSI C... no
+configure: error: MySQL requires an ANSI C compiler (and a C++ compiler).
+Try gcc. See the Installation chapter in the Reference Manual.
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          Another reason for not being able to compile is that you did
+          not define the <literal>+DD64</literal> flags as just
+          described.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
 </section>


Modified: trunk/refman-5.5/installing-aix.xml
===================================================================
--- trunk/refman-5.5/installing-aix.xml	2010-11-16 20:03:22 UTC (rev 23787)
+++ trunk/refman-5.5/installing-aix.xml	2010-11-16 20:03:31 UTC (rev 23788)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 101; 3609 bytes

@@ -69,105 +69,4 @@
 
   </section>
 
-  <section id="aix-installation-source">
-
-    <title>Notes on Installing MySQL on AIX from Source</title>
-
-    <para>
-      General notes on building MySQL from source on IBM AIX:
-    </para>
-
-    <itemizedlist>
-
-      <listitem>
-        <para>
-          Automatic detection of <literal>xlC</literal> is missing from
-          Autoconf, so a number of variables need to be set before
-          running <command>configure</command>. The following example
-          uses the IBM compiler:
-        </para>
-
-<programlisting>
-export CC="xlc_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192 "
-export CXX="xlC_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192"
-export CFLAGS="-I /usr/local/include"
-export LDFLAGS="-L /usr/local/lib"
-export CPPFLAGS=$CFLAGS
-export CXXFLAGS=$CFLAGS
-
-./configure --prefix=/usr/local \
-                --localstatedir=/var/mysql \
-                --sbindir='/usr/local/bin' \
-                --libexecdir='/usr/local/bin' \
-                --enable-thread-safe-client \
-                --enable-large-files
-</programlisting>
-
-        <para>
-          The preceding options are used to compile the MySQL
-          distribution that can be found at
-          <ulink url="http://www-frec.bull.com/"/>.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you change the <option>-O3</option> to <option>-O2</option>
-          in the preceding <command>configure</command> line, you must
-          also remove the <option>-qstrict</option> option. This is a
-          limitation in the IBM C compiler.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you are using <command>gcc</command> to compile MySQL, you
-          <emphasis>must</emphasis> use the
-          <option>-fno-exceptions</option> flag, because the exception
-          handling in <command>gcc</command> is not thread-safe. There
-          are also some known problems with IBM's assembler that may
-          cause it to generate bad code when used with
-          <command>gcc</command>.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you have problems with signals (MySQL dies unexpectedly
-          under high load), you may have found an OS bug with threads
-          and signals. In this case, you can tell MySQL not to use
-          signals by configuring as follows:
-        </para>
-
-<programlisting>
-CFLAGS=-DDONT_USE_THR_ALARM CXX=gcc \
-CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti \
--DDONT_USE_THR_ALARM" \
-./configure --prefix=/usr/local/mysql --with-debug \
-    --with-low-memory
-</programlisting>
-
-        <para>
-          This does not affect the performance of MySQL, but has the
-          side effect that you cannot kill clients that are
-          <quote>sleeping</quote> on a connection with
-          <command>mysqladmin kill</command> or <command>mysqladmin
-          shutdown</command>. Instead, the client dies when it issues
-          its next command.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          On some versions of AIX, linking with
-          <literal>libbind.a</literal> makes
-          <literal>getservbyname()</literal> dump core. This is an AIX
-          bug and should be reported to IBM.
-        </para>
-      </listitem>
-
-    </itemizedlist>
-
-  </section>
-
 </section>


Modified: trunk/refman-5.5/installing-hpux.xml
===================================================================
--- trunk/refman-5.5/installing-hpux.xml	2010-11-16 20:03:22 UTC (rev 23787)
+++ trunk/refman-5.5/installing-hpux.xml	2010-11-16 20:03:31 UTC (rev 23788)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 59; 1925 bytes

@@ -104,65 +104,6 @@
 
   </section>
 
-  <section id="hpux-installation-source">
-
-    <title>Notes on Installing MySQL on HP-UX from Source</title>
-
-    <para>
-      Additional notes on compiling MySQL on HP-UX.
-    </para>
-
-    <itemizedlist>
-
-      <listitem>
-        <para>
-          If you are using HP-UX compiler, you can use the following
-          command (which has been tested with <command>cc</command>
-          B.11.11.04):
-        </para>
-
-<programlisting>
-CC=cc CXX=aCC CFLAGS=+DD64 CXXFLAGS=+DD64 ./configure \
-    --with-extra-character-set=complex
-</programlisting>
-
-        <para>
-          You can ignore any errors of the following type:
-        </para>
-
-<programlisting>
-aCC: warning 901: unknown option: `-3': use +help for online
-documentation
-</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you get the following error from
-          <command>configure</command>, verify that you do not have the
-          path to the K&amp;R compiler before the path to the HP-UX C
-          and C++ compiler:
-        </para>
-
-<programlisting>
-checking for cc option to accept ANSI C... no
-configure: error: MySQL requires an ANSI C compiler (and a C++ compiler).
-Try gcc. See the Installation chapter in the Reference Manual.
-</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Another reason for not being able to compile is that you did
-          not define the <literal>+DD64</literal> flags as just
-          described.
-        </para>
-      </listitem>
-
-    </itemizedlist>
-
-  </section>
-
   <section id="hpux-installation-depot">
 
     <title>Installing MySQL on HP-UX using DEPOT</title>


Modified: trunk/refman-5.5/installing-solaris.xml
===================================================================
--- trunk/refman-5.5/installing-solaris.xml	2010-11-16 20:03:22 UTC (rev 23787)
+++ trunk/refman-5.5/installing-solaris.xml	2010-11-16 20:03:31 UTC (rev 23788)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 239; 7990 bytes

@@ -411,243 +411,4 @@
 
   </section>
 
-  <section id="solaris-installation-source">
-
-    <title>Notes on Installing MySQL on Solaris from Source</title>
-
-    <para>
-      When building MySQL on Solaris you can use either the Sun Studio
-      or GNU cc compilers. For more information on specific notes and
-      environments, use the following hints.
-    </para>
-
-    <itemizedlist>
-
-      <listitem>
-        <para>
-          When building you should ensure that your
-          <literal>PATH</literal> variable includes the necessary tools,
-          including <command>ar</command> for building libraries. Some
-          tools are located in <filename>/usr/ccs/bin</filename>.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          When running <command>configure</command>, you should specify
-          the C and C++ compiler explicitly to ensure that the right C
-          compiler combination is used:
-        </para>
-
-<programlisting>$ configure CC=gcc CXX=g++</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          For detailed information on performance tuning your MySQL
-          installation for Solaris, you can use the information from
-          <ulink url="http://blogs.sun.com/krishs/entry/sun_studio_compiler_options_for">Krish
-          Shankar</ulink> and the
-          <ulink url="http://developers.sun.com/solaris/articles/mysql_perf_tune.html">Sun
-          Solaris MySQL Performance Tuning</ulink> pages.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you have an UltraSPARC system, you can get 4% better
-          performance by adding <option>-mcpu=v8
-          -Wa,-xarch=v8plusa</option> to the <literal>CFLAGS</literal>
-          and <literal>CXXFLAGS</literal> environment variables.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you have Sun's Forte 5.00 (or newer) or Sun Studio
-          compiler, you can run <command>configure</command> like this:
-        </para>
-
-<programlisting>
-CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt" \
-CXX=CC CXXFLAGS="-noex -mt" \
-./configure --prefix=/usr/local/mysql --enable-assembler
-</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          To create a 64-bit SPARC binary with Sun's Forte or Sun Studio
-          compiler, use the following configuration options:
-        </para>
-
-<programlisting>
-CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt -xarch=v9" \
-CXX=CC CXXFLAGS="-noex -mt -xarch=v9" ASFLAGS="-xarch=v9" \
-./configure --prefix=/usr/local/mysql --enable-assembler
-</programlisting>
-
-        <para>
-          To create a 64-bit Solaris binary using
-          <command>gcc</command>, add <option>-m64</option> to
-          <literal>CFLAGS</literal> and <literal>CXXFLAGS</literal> and
-          remove <option>--enable-assembler</option> from the
-          <command>configure</command> line.
-        </para>
-
-        <para>
-          In the MySQL benchmarks, we obtained a 4% speed increase on
-          UltraSPARC when using Forte 5.0 in 32-bit mode, as compared to
-          using <command>gcc</command> 3.2 with the
-          <option>-mcpu</option> flag.
-        </para>
-
-        <para>
-          If you create a 64-bit <command>mysqld</command> binary, it is
-          4% slower than the 32-bit binary, but can handle more threads
-          and memory.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you get a problem with <literal>fdatasync</literal> or
-          <literal>sched_yield</literal>, you can fix this by adding
-          <literal>LIBS=-lrt</literal> to the
-          <command>configure</command> line
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          Solaris does not provide static versions of all system
-          libraries (<literal>libpthreads</literal> and
-          <literal>libdl</literal>), so you cannot compile MySQL with
-          <option>--static</option>. If you try to do so, you get one of
-          the following errors:
-        </para>
-
-<programlisting>
-ld: fatal: library -ldl: not found
-undefined reference to `dlopen'
-cannot find -lrt
-</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you link your own MySQL client programs, you may see the
-          following error at runtime:
-        </para>
-
-<programlisting>
-ld.so.1: fatal: libmysqlclient.so.#:
-open failed: No such file or directory
-</programlisting>
-
-        <para>
-          This problem can be avoided by one of the following methods:
-        </para>
-
-        <itemizedlist>
-
-          <listitem>
-            <para>
-              Use the <literal>crle</literal> tool to add the directory
-              containing the <literal>libmysqlclient</literal> library
-              file to the list of standard library directories. You need
-              administrator privileges to do this. Make sure you update
-              the library information, rather than replace it with the
-              new path. For example, the following command adds the
-              directory to the list of standard directories searched for
-              libraries.
-            </para>
-
-<programlisting>shell&gt; crle -u -l /usr/local/mysql/lib</programlisting>
-
-            <para>
-              For 64-bit libraries, add the <literal>-64</literal>
-              option:
-            </para>
-
-<programlisting>shell&gt; crle -64 -u -l /usr/local/mysql/lib</programlisting>
-          </listitem>
-
-          <listitem>
-            <para>
-              Link clients with the
-              <option>-Wl,r/full/path/to/libmysqlclient.so</option> flag
-              rather than with <option>-Lpath</option>).
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
-              Copy <literal>libmysqclient.so</literal> to
-              <filename>/usr/lib</filename>.
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
-              <indexterm>
-                <primary>LD_RUN_PATH environment variable</primary>
-              </indexterm>
-
-              <indexterm>
-                <primary>environment variable</primary>
-                <secondary>LD_RUN_PATH</secondary>
-              </indexterm>
-
-              Add the path name of the directory where
-              <filename>libmysqlclient.so</filename> is located to the
-              <literal>LD_RUN_PATH</literal> environment variable before
-              running your client.
-            </para>
-          </listitem>
-
-        </itemizedlist>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you have problems with <command>configure</command> trying
-          to link with <option>-lz</option> when you do not have
-          <literal>zlib</literal> installed, you have two options:
-        </para>
-
-        <itemizedlist>
-
-          <listitem>
-            <para>
-              If you want to be able to use the compressed communication
-              protocol, you need to get and install
-              <literal>zlib</literal> from
-              <literal>ftp.gnu.org</literal>.
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
-              Run <command>configure</command> with the
-              <option>--with-named-z-libs=no</option> option when
-              building MySQL.
-            </para>
-          </listitem>
-
-        </itemizedlist>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you are using <command>gcc</command> and have problems with
-          loading user-defined functions (UDFs) into MySQL, try adding
-          <option>-lgcc</option> to the link line for the UDF.
-        </para>
-      </listitem>
-
-    </itemizedlist>
-
-  </section>
-
 </section>


Modified: trunk/refman-5.5/installing-source-core.xml
===================================================================
--- trunk/refman-5.5/installing-source-core.xml	2010-11-16 20:03:22 UTC (rev 23787)
+++ trunk/refman-5.5/installing-source-core.xml	2010-11-16 20:03:31 UTC (rev 23788)
Changed blocks: 1, Lines Added: 399, Lines Deleted: 0; 12832 bytes

@@ -3131,4 +3131,403 @@
 
   </section>
 
+  <section id="solaris-installation-source">
+
+    <title>Notes on Installing MySQL on Solaris from Source</title>
+
+    <para>
+      When building MySQL on Solaris you can use either the Sun Studio
+      or GNU cc compilers. For more information on specific notes and
+      environments, use the following hints.
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          When building you should ensure that your
+          <literal>PATH</literal> variable includes the necessary tools,
+          including <command>ar</command> for building libraries. Some
+          tools are located in <filename>/usr/ccs/bin</filename>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          When running <command>configure</command>, you should specify
+          the C and C++ compiler explicitly to ensure that the right C
+          compiler combination is used:
+        </para>
+
+<programlisting>$ configure CC=gcc CXX=g++</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          For detailed information on performance tuning your MySQL
+          installation for Solaris, you can use the information from
+          <ulink url="http://blogs.sun.com/krishs/entry/sun_studio_compiler_options_for">Krish
+          Shankar</ulink> and the
+          <ulink url="http://developers.sun.com/solaris/articles/mysql_perf_tune.html">Sun
+          Solaris MySQL Performance Tuning</ulink> pages.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you have an UltraSPARC system, you can get 4% better
+          performance by adding <option>-mcpu=v8
+          -Wa,-xarch=v8plusa</option> to the <literal>CFLAGS</literal>
+          and <literal>CXXFLAGS</literal> environment variables.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you have Sun's Forte 5.00 (or newer) or Sun Studio
+          compiler, you can run <command>configure</command> like this:
+        </para>
+
+<programlisting>
+CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt" \
+CXX=CC CXXFLAGS="-noex -mt" \
+./configure --prefix=/usr/local/mysql --enable-assembler
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          To create a 64-bit SPARC binary with Sun's Forte or Sun Studio
+          compiler, use the following configuration options:
+        </para>
+
+<programlisting>
+CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt -xarch=v9" \
+CXX=CC CXXFLAGS="-noex -mt -xarch=v9" ASFLAGS="-xarch=v9" \
+./configure --prefix=/usr/local/mysql --enable-assembler
+</programlisting>
+
+        <para>
+          To create a 64-bit Solaris binary using
+          <command>gcc</command>, add <option>-m64</option> to
+          <literal>CFLAGS</literal> and <literal>CXXFLAGS</literal> and
+          remove <option>--enable-assembler</option> from the
+          <command>configure</command> line.
+        </para>
+
+        <para>
+          In the MySQL benchmarks, we obtained a 4% speed increase on
+          UltraSPARC when using Forte 5.0 in 32-bit mode, as compared to
+          using <command>gcc</command> 3.2 with the
+          <option>-mcpu</option> flag.
+        </para>
+
+        <para>
+          If you create a 64-bit <command>mysqld</command> binary, it is
+          4% slower than the 32-bit binary, but can handle more threads
+          and memory.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you get a problem with <literal>fdatasync</literal> or
+          <literal>sched_yield</literal>, you can fix this by adding
+          <literal>LIBS=-lrt</literal> to the
+          <command>configure</command> line
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Solaris does not provide static versions of all system
+          libraries (<literal>libpthreads</literal> and
+          <literal>libdl</literal>), so you cannot compile MySQL with
+          <option>--static</option>. If you try to do so, you get one of
+          the following errors:
+        </para>
+
+<programlisting>
+ld: fatal: library -ldl: not found
+undefined reference to `dlopen'
+cannot find -lrt
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you link your own MySQL client programs, you may see the
+          following error at runtime:
+        </para>
+
+<programlisting>
+ld.so.1: fatal: libmysqlclient.so.#:
+open failed: No such file or directory
+</programlisting>
+
+        <para>
+          This problem can be avoided by one of the following methods:
+        </para>
+
+        <itemizedlist>
+
+          <listitem>
+            <para>
+              Use the <literal>crle</literal> tool to add the directory
+              containing the <literal>libmysqlclient</literal> library
+              file to the list of standard library directories. You need
+              administrator privileges to do this. Make sure you update
+              the library information, rather than replace it with the
+              new path. For example, the following command adds the
+              directory to the list of standard directories searched for
+              libraries.
+            </para>
+
+<programlisting>shell&gt; crle -u -l /usr/local/mysql/lib</programlisting>
+
+            <para>
+              For 64-bit libraries, add the <literal>-64</literal>
+              option:
+            </para>
+
+<programlisting>shell&gt; crle -64 -u -l /usr/local/mysql/lib</programlisting>
+          </listitem>
+
+          <listitem>
+            <para>
+              Link clients with the
+              <option>-Wl,r/full/path/to/libmysqlclient.so</option> flag
+              rather than with <option>-Lpath</option>).
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              Copy <literal>libmysqclient.so</literal> to
+              <filename>/usr/lib</filename>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <indexterm>
+                <primary>LD_RUN_PATH environment variable</primary>
+              </indexterm>
+
+              <indexterm>
+                <primary>environment variable</primary>
+                <secondary>LD_RUN_PATH</secondary>
+              </indexterm>
+
+              Add the path name of the directory where
+              <filename>libmysqlclient.so</filename> is located to the
+              <literal>LD_RUN_PATH</literal> environment variable before
+              running your client.
+            </para>
+          </listitem>
+
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you have problems with <command>configure</command> trying
+          to link with <option>-lz</option> when you do not have
+          <literal>zlib</literal> installed, you have two options:
+        </para>
+
+        <itemizedlist>
+
+          <listitem>
+            <para>
+              If you want to be able to use the compressed communication
+              protocol, you need to get and install
+              <literal>zlib</literal> from
+              <literal>ftp.gnu.org</literal>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              Run <command>configure</command> with the
+              <option>--with-named-z-libs=no</option> option when
+              building MySQL.
+            </para>
+          </listitem>
+
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you are using <command>gcc</command> and have problems with
+          loading user-defined functions (UDFs) into MySQL, try adding
+          <option>-lgcc</option> to the link line for the UDF.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
+  <section id="aix-installation-source">
+
+    <title>Notes on Installing MySQL on AIX from Source</title>
+
+    <para>
+      General notes on building MySQL from source on IBM AIX:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          Automatic detection of <literal>xlC</literal> is missing from
+          Autoconf, so a number of variables need to be set before
+          running <command>configure</command>. The following example
+          uses the IBM compiler:
+        </para>
+
+<programlisting>
+export CC="xlc_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192 "
+export CXX="xlC_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192"
+export CFLAGS="-I /usr/local/include"
+export LDFLAGS="-L /usr/local/lib"
+export CPPFLAGS=$CFLAGS
+export CXXFLAGS=$CFLAGS
+
+./configure --prefix=/usr/local \
+                --localstatedir=/var/mysql \
+                --sbindir='/usr/local/bin' \
+                --libexecdir='/usr/local/bin' \
+                --enable-thread-safe-client \
+                --enable-large-files
+</programlisting>
+
+        <para>
+          The preceding options are used to compile the MySQL
+          distribution that can be found at
+          <ulink url="http://www-frec.bull.com/"/>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you change the <option>-O3</option> to <option>-O2</option>
+          in the preceding <command>configure</command> line, you must
+          also remove the <option>-qstrict</option> option. This is a
+          limitation in the IBM C compiler.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you are using <command>gcc</command> to compile MySQL, you
+          <emphasis>must</emphasis> use the
+          <option>-fno-exceptions</option> flag, because the exception
+          handling in <command>gcc</command> is not thread-safe. There
+          are also some known problems with IBM's assembler that may
+          cause it to generate bad code when used with
+          <command>gcc</command>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you have problems with signals (MySQL dies unexpectedly
+          under high load), you may have found an OS bug with threads
+          and signals. In this case, you can tell MySQL not to use
+          signals by configuring as follows:
+        </para>
+
+<programlisting>
+CFLAGS=-DDONT_USE_THR_ALARM CXX=gcc \
+CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti \
+-DDONT_USE_THR_ALARM" \
+./configure --prefix=/usr/local/mysql --with-debug \
+    --with-low-memory
+</programlisting>
+
+        <para>
+          This does not affect the performance of MySQL, but has the
+          side effect that you cannot kill clients that are
+          <quote>sleeping</quote> on a connection with
+          <command>mysqladmin kill</command> or <command>mysqladmin
+          shutdown</command>. Instead, the client dies when it issues
+          its next command.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          On some versions of AIX, linking with
+          <literal>libbind.a</literal> makes
+          <literal>getservbyname()</literal> dump core. This is an AIX
+          bug and should be reported to IBM.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
+  <section id="hpux-installation-source">
+
+    <title>Notes on Installing MySQL on HP-UX from Source</title>
+
+    <para>
+      Additional notes on compiling MySQL on HP-UX.
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          If you are using HP-UX compiler, you can use the following
+          command (which has been tested with <command>cc</command>
+          B.11.11.04):
+        </para>
+
+<programlisting>
+CC=cc CXX=aCC CFLAGS=+DD64 CXXFLAGS=+DD64 ./configure \
+    --with-extra-character-set=complex
+</programlisting>
+
+        <para>
+          You can ignore any errors of the following type:
+        </para>
+
+<programlisting>
+aCC: warning 901: unknown option: `-3': use +help for online
+documentation
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you get the following error from
+          <command>configure</command>, verify that you do not have the
+          path to the K&amp;R compiler before the path to the HP-UX C
+          and C++ compiler:
+        </para>
+
+<programlisting>
+checking for cc option to accept ANSI C... no
+configure: error: MySQL requires an ANSI C compiler (and a C++ compiler).
+Try gcc. See the Installation chapter in the Reference Manual.
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          Another reason for not being able to compile is that you did
+          not define the <literal>+DD64</literal> flags as just
+          described.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
 </section>


Modified: trunk/refman-5.6/installing-aix.xml
===================================================================
--- trunk/refman-5.6/installing-aix.xml	2010-11-16 20:03:22 UTC (rev 23787)
+++ trunk/refman-5.6/installing-aix.xml	2010-11-16 20:03:31 UTC (rev 23788)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 101; 3609 bytes

@@ -69,105 +69,4 @@
 
   </section>
 
-  <section id="aix-installation-source">
-
-    <title>Notes on Installing MySQL on AIX from Source</title>
-
-    <para>
-      General notes on building MySQL from source on IBM AIX:
-    </para>
-
-    <itemizedlist>
-
-      <listitem>
-        <para>
-          Automatic detection of <literal>xlC</literal> is missing from
-          Autoconf, so a number of variables need to be set before
-          running <command>configure</command>. The following example
-          uses the IBM compiler:
-        </para>
-
-<programlisting>
-export CC="xlc_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192 "
-export CXX="xlC_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192"
-export CFLAGS="-I /usr/local/include"
-export LDFLAGS="-L /usr/local/lib"
-export CPPFLAGS=$CFLAGS
-export CXXFLAGS=$CFLAGS
-
-./configure --prefix=/usr/local \
-                --localstatedir=/var/mysql \
-                --sbindir='/usr/local/bin' \
-                --libexecdir='/usr/local/bin' \
-                --enable-thread-safe-client \
-                --enable-large-files
-</programlisting>
-
-        <para>
-          The preceding options are used to compile the MySQL
-          distribution that can be found at
-          <ulink url="http://www-frec.bull.com/"/>.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you change the <option>-O3</option> to <option>-O2</option>
-          in the preceding <command>configure</command> line, you must
-          also remove the <option>-qstrict</option> option. This is a
-          limitation in the IBM C compiler.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you are using <command>gcc</command> to compile MySQL, you
-          <emphasis>must</emphasis> use the
-          <option>-fno-exceptions</option> flag, because the exception
-          handling in <command>gcc</command> is not thread-safe. There
-          are also some known problems with IBM's assembler that may
-          cause it to generate bad code when used with
-          <command>gcc</command>.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you have problems with signals (MySQL dies unexpectedly
-          under high load), you may have found an OS bug with threads
-          and signals. In this case, you can tell MySQL not to use
-          signals by configuring as follows:
-        </para>
-
-<programlisting>
-CFLAGS=-DDONT_USE_THR_ALARM CXX=gcc \
-CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti \
--DDONT_USE_THR_ALARM" \
-./configure --prefix=/usr/local/mysql --with-debug \
-    --with-low-memory
-</programlisting>
-
-        <para>
-          This does not affect the performance of MySQL, but has the
-          side effect that you cannot kill clients that are
-          <quote>sleeping</quote> on a connection with
-          <command>mysqladmin kill</command> or <command>mysqladmin
-          shutdown</command>. Instead, the client dies when it issues
-          its next command.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          On some versions of AIX, linking with
-          <literal>libbind.a</literal> makes
-          <literal>getservbyname()</literal> dump core. This is an AIX
-          bug and should be reported to IBM.
-        </para>
-      </listitem>
-
-    </itemizedlist>
-
-  </section>
-
 </section>


Modified: trunk/refman-5.6/installing-hpux.xml
===================================================================
--- trunk/refman-5.6/installing-hpux.xml	2010-11-16 20:03:22 UTC (rev 23787)
+++ trunk/refman-5.6/installing-hpux.xml	2010-11-16 20:03:31 UTC (rev 23788)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 59; 1925 bytes

@@ -104,65 +104,6 @@
 
   </section>
 
-  <section id="hpux-installation-source">
-
-    <title>Notes on Installing MySQL on HP-UX from Source</title>
-
-    <para>
-      Additional notes on compiling MySQL on HP-UX.
-    </para>
-
-    <itemizedlist>
-
-      <listitem>
-        <para>
-          If you are using HP-UX compiler, you can use the following
-          command (which has been tested with <command>cc</command>
-          B.11.11.04):
-        </para>
-
-<programlisting>
-CC=cc CXX=aCC CFLAGS=+DD64 CXXFLAGS=+DD64 ./configure \
-    --with-extra-character-set=complex
-</programlisting>
-
-        <para>
-          You can ignore any errors of the following type:
-        </para>
-
-<programlisting>
-aCC: warning 901: unknown option: `-3': use +help for online
-documentation
-</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you get the following error from
-          <command>configure</command>, verify that you do not have the
-          path to the K&amp;R compiler before the path to the HP-UX C
-          and C++ compiler:
-        </para>
-
-<programlisting>
-checking for cc option to accept ANSI C... no
-configure: error: MySQL requires an ANSI C compiler (and a C++ compiler).
-Try gcc. See the Installation chapter in the Reference Manual.
-</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          Another reason for not being able to compile is that you did
-          not define the <literal>+DD64</literal> flags as just
-          described.
-        </para>
-      </listitem>
-
-    </itemizedlist>
-
-  </section>
-
   <section id="hpux-installation-depot">
 
     <title>Installing MySQL on HP-UX using DEPOT</title>


Modified: trunk/refman-5.6/installing-solaris.xml
===================================================================
--- trunk/refman-5.6/installing-solaris.xml	2010-11-16 20:03:22 UTC (rev 23787)
+++ trunk/refman-5.6/installing-solaris.xml	2010-11-16 20:03:31 UTC (rev 23788)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 239; 7990 bytes

@@ -411,243 +411,4 @@
 
   </section>
 
-  <section id="solaris-installation-source">
-
-    <title>Notes on Installing MySQL on Solaris from Source</title>
-
-    <para>
-      When building MySQL on Solaris you can use either the Sun Studio
-      or GNU cc compilers. For more information on specific notes and
-      environments, use the following hints.
-    </para>
-
-    <itemizedlist>
-
-      <listitem>
-        <para>
-          When building you should ensure that your
-          <literal>PATH</literal> variable includes the necessary tools,
-          including <command>ar</command> for building libraries. Some
-          tools are located in <filename>/usr/ccs/bin</filename>.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          When running <command>configure</command>, you should specify
-          the C and C++ compiler explicitly to ensure that the right C
-          compiler combination is used:
-        </para>
-
-<programlisting>$ configure CC=gcc CXX=g++</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          For detailed information on performance tuning your MySQL
-          installation for Solaris, you can use the information from
-          <ulink url="http://blogs.sun.com/krishs/entry/sun_studio_compiler_options_for">Krish
-          Shankar</ulink> and the
-          <ulink url="http://developers.sun.com/solaris/articles/mysql_perf_tune.html">Sun
-          Solaris MySQL Performance Tuning</ulink> pages.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you have an UltraSPARC system, you can get 4% better
-          performance by adding <option>-mcpu=v8
-          -Wa,-xarch=v8plusa</option> to the <literal>CFLAGS</literal>
-          and <literal>CXXFLAGS</literal> environment variables.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you have Sun's Forte 5.00 (or newer) or Sun Studio
-          compiler, you can run <command>configure</command> like this:
-        </para>
-
-<programlisting>
-CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt" \
-CXX=CC CXXFLAGS="-noex -mt" \
-./configure --prefix=/usr/local/mysql --enable-assembler
-</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          To create a 64-bit SPARC binary with Sun's Forte or Sun Studio
-          compiler, use the following configuration options:
-        </para>
-
-<programlisting>
-CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt -xarch=v9" \
-CXX=CC CXXFLAGS="-noex -mt -xarch=v9" ASFLAGS="-xarch=v9" \
-./configure --prefix=/usr/local/mysql --enable-assembler
-</programlisting>
-
-        <para>
-          To create a 64-bit Solaris binary using
-          <command>gcc</command>, add <option>-m64</option> to
-          <literal>CFLAGS</literal> and <literal>CXXFLAGS</literal> and
-          remove <option>--enable-assembler</option> from the
-          <command>configure</command> line.
-        </para>
-
-        <para>
-          In the MySQL benchmarks, we obtained a 4% speed increase on
-          UltraSPARC when using Forte 5.0 in 32-bit mode, as compared to
-          using <command>gcc</command> 3.2 with the
-          <option>-mcpu</option> flag.
-        </para>
-
-        <para>
-          If you create a 64-bit <command>mysqld</command> binary, it is
-          4% slower than the 32-bit binary, but can handle more threads
-          and memory.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you get a problem with <literal>fdatasync</literal> or
-          <literal>sched_yield</literal>, you can fix this by adding
-          <literal>LIBS=-lrt</literal> to the
-          <command>configure</command> line
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          Solaris does not provide static versions of all system
-          libraries (<literal>libpthreads</literal> and
-          <literal>libdl</literal>), so you cannot compile MySQL with
-          <option>--static</option>. If you try to do so, you get one of
-          the following errors:
-        </para>
-
-<programlisting>
-ld: fatal: library -ldl: not found
-undefined reference to `dlopen'
-cannot find -lrt
-</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you link your own MySQL client programs, you may see the
-          following error at runtime:
-        </para>
-
-<programlisting>
-ld.so.1: fatal: libmysqlclient.so.#:
-open failed: No such file or directory
-</programlisting>
-
-        <para>
-          This problem can be avoided by one of the following methods:
-        </para>
-
-        <itemizedlist>
-
-          <listitem>
-            <para>
-              Use the <literal>crle</literal> tool to add the directory
-              containing the <literal>libmysqlclient</literal> library
-              file to the list of standard library directories. You need
-              administrator privileges to do this. Make sure you update
-              the library information, rather than replace it with the
-              new path. For example, the following command adds the
-              directory to the list of standard directories searched for
-              libraries.
-            </para>
-
-<programlisting>shell&gt; crle -u -l /usr/local/mysql/lib</programlisting>
-
-            <para>
-              For 64-bit libraries, add the <literal>-64</literal>
-              option:
-            </para>
-
-<programlisting>shell&gt; crle -64 -u -l /usr/local/mysql/lib</programlisting>
-          </listitem>
-
-          <listitem>
-            <para>
-              Link clients with the
-              <option>-Wl,r/full/path/to/libmysqlclient.so</option> flag
-              rather than with <option>-Lpath</option>).
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
-              Copy <literal>libmysqclient.so</literal> to
-              <filename>/usr/lib</filename>.
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
-              <indexterm>
-                <primary>LD_RUN_PATH environment variable</primary>
-              </indexterm>
-
-              <indexterm>
-                <primary>environment variable</primary>
-                <secondary>LD_RUN_PATH</secondary>
-              </indexterm>
-
-              Add the path name of the directory where
-              <filename>libmysqlclient.so</filename> is located to the
-              <literal>LD_RUN_PATH</literal> environment variable before
-              running your client.
-            </para>
-          </listitem>
-
-        </itemizedlist>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you have problems with <command>configure</command> trying
-          to link with <option>-lz</option> when you do not have
-          <literal>zlib</literal> installed, you have two options:
-        </para>
-
-        <itemizedlist>
-
-          <listitem>
-            <para>
-              If you want to be able to use the compressed communication
-              protocol, you need to get and install
-              <literal>zlib</literal> from
-              <literal>ftp.gnu.org</literal>.
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
-              Run <command>configure</command> with the
-              <option>--with-named-z-libs=no</option> option when
-              building MySQL.
-            </para>
-          </listitem>
-
-        </itemizedlist>
-      </listitem>
-
-      <listitem>
-        <para>
-          If you are using <command>gcc</command> and have problems with
-          loading user-defined functions (UDFs) into MySQL, try adding
-          <option>-lgcc</option> to the link line for the UDF.
-        </para>
-      </listitem>
-
-    </itemizedlist>
-
-  </section>
-
 </section>


Modified: trunk/refman-5.6/installing-source-core.xml
===================================================================
--- trunk/refman-5.6/installing-source-core.xml	2010-11-16 20:03:22 UTC (rev 23787)
+++ trunk/refman-5.6/installing-source-core.xml	2010-11-16 20:03:31 UTC (rev 23788)
Changed blocks: 1, Lines Added: 399, Lines Deleted: 0; 12832 bytes

@@ -3131,4 +3131,403 @@
 
   </section>
 
+  <section id="solaris-installation-source">
+
+    <title>Notes on Installing MySQL on Solaris from Source</title>
+
+    <para>
+      When building MySQL on Solaris you can use either the Sun Studio
+      or GNU cc compilers. For more information on specific notes and
+      environments, use the following hints.
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          When building you should ensure that your
+          <literal>PATH</literal> variable includes the necessary tools,
+          including <command>ar</command> for building libraries. Some
+          tools are located in <filename>/usr/ccs/bin</filename>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          When running <command>configure</command>, you should specify
+          the C and C++ compiler explicitly to ensure that the right C
+          compiler combination is used:
+        </para>
+
+<programlisting>$ configure CC=gcc CXX=g++</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          For detailed information on performance tuning your MySQL
+          installation for Solaris, you can use the information from
+          <ulink url="http://blogs.sun.com/krishs/entry/sun_studio_compiler_options_for">Krish
+          Shankar</ulink> and the
+          <ulink url="http://developers.sun.com/solaris/articles/mysql_perf_tune.html">Sun
+          Solaris MySQL Performance Tuning</ulink> pages.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you have an UltraSPARC system, you can get 4% better
+          performance by adding <option>-mcpu=v8
+          -Wa,-xarch=v8plusa</option> to the <literal>CFLAGS</literal>
+          and <literal>CXXFLAGS</literal> environment variables.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you have Sun's Forte 5.00 (or newer) or Sun Studio
+          compiler, you can run <command>configure</command> like this:
+        </para>
+
+<programlisting>
+CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt" \
+CXX=CC CXXFLAGS="-noex -mt" \
+./configure --prefix=/usr/local/mysql --enable-assembler
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          To create a 64-bit SPARC binary with Sun's Forte or Sun Studio
+          compiler, use the following configuration options:
+        </para>
+
+<programlisting>
+CC=cc CFLAGS="-Xa -fast -native -xstrconst -mt -xarch=v9" \
+CXX=CC CXXFLAGS="-noex -mt -xarch=v9" ASFLAGS="-xarch=v9" \
+./configure --prefix=/usr/local/mysql --enable-assembler
+</programlisting>
+
+        <para>
+          To create a 64-bit Solaris binary using
+          <command>gcc</command>, add <option>-m64</option> to
+          <literal>CFLAGS</literal> and <literal>CXXFLAGS</literal> and
+          remove <option>--enable-assembler</option> from the
+          <command>configure</command> line.
+        </para>
+
+        <para>
+          In the MySQL benchmarks, we obtained a 4% speed increase on
+          UltraSPARC when using Forte 5.0 in 32-bit mode, as compared to
+          using <command>gcc</command> 3.2 with the
+          <option>-mcpu</option> flag.
+        </para>
+
+        <para>
+          If you create a 64-bit <command>mysqld</command> binary, it is
+          4% slower than the 32-bit binary, but can handle more threads
+          and memory.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you get a problem with <literal>fdatasync</literal> or
+          <literal>sched_yield</literal>, you can fix this by adding
+          <literal>LIBS=-lrt</literal> to the
+          <command>configure</command> line
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Solaris does not provide static versions of all system
+          libraries (<literal>libpthreads</literal> and
+          <literal>libdl</literal>), so you cannot compile MySQL with
+          <option>--static</option>. If you try to do so, you get one of
+          the following errors:
+        </para>
+
+<programlisting>
+ld: fatal: library -ldl: not found
+undefined reference to `dlopen'
+cannot find -lrt
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you link your own MySQL client programs, you may see the
+          following error at runtime:
+        </para>
+
+<programlisting>
+ld.so.1: fatal: libmysqlclient.so.#:
+open failed: No such file or directory
+</programlisting>
+
+        <para>
+          This problem can be avoided by one of the following methods:
+        </para>
+
+        <itemizedlist>
+
+          <listitem>
+            <para>
+              Use the <literal>crle</literal> tool to add the directory
+              containing the <literal>libmysqlclient</literal> library
+              file to the list of standard library directories. You need
+              administrator privileges to do this. Make sure you update
+              the library information, rather than replace it with the
+              new path. For example, the following command adds the
+              directory to the list of standard directories searched for
+              libraries.
+            </para>
+
+<programlisting>shell&gt; crle -u -l /usr/local/mysql/lib</programlisting>
+
+            <para>
+              For 64-bit libraries, add the <literal>-64</literal>
+              option:
+            </para>
+
+<programlisting>shell&gt; crle -64 -u -l /usr/local/mysql/lib</programlisting>
+          </listitem>
+
+          <listitem>
+            <para>
+              Link clients with the
+              <option>-Wl,r/full/path/to/libmysqlclient.so</option> flag
+              rather than with <option>-Lpath</option>).
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              Copy <literal>libmysqclient.so</literal> to
+              <filename>/usr/lib</filename>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <indexterm>
+                <primary>LD_RUN_PATH environment variable</primary>
+              </indexterm>
+
+              <indexterm>
+                <primary>environment variable</primary>
+                <secondary>LD_RUN_PATH</secondary>
+              </indexterm>
+
+              Add the path name of the directory where
+              <filename>libmysqlclient.so</filename> is located to the
+              <literal>LD_RUN_PATH</literal> environment variable before
+              running your client.
+            </para>
+          </listitem>
+
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you have problems with <command>configure</command> trying
+          to link with <option>-lz</option> when you do not have
+          <literal>zlib</literal> installed, you have two options:
+        </para>
+
+        <itemizedlist>
+
+          <listitem>
+            <para>
+              If you want to be able to use the compressed communication
+              protocol, you need to get and install
+              <literal>zlib</literal> from
+              <literal>ftp.gnu.org</literal>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              Run <command>configure</command> with the
+              <option>--with-named-z-libs=no</option> option when
+              building MySQL.
+            </para>
+          </listitem>
+
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you are using <command>gcc</command> and have problems with
+          loading user-defined functions (UDFs) into MySQL, try adding
+          <option>-lgcc</option> to the link line for the UDF.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
+  <section id="aix-installation-source">
+
+    <title>Notes on Installing MySQL on AIX from Source</title>
+
+    <para>
+      General notes on building MySQL from source on IBM AIX:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          Automatic detection of <literal>xlC</literal> is missing from
+          Autoconf, so a number of variables need to be set before
+          running <command>configure</command>. The following example
+          uses the IBM compiler:
+        </para>
+
+<programlisting>
+export CC="xlc_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192 "
+export CXX="xlC_r -ma -O3 -qstrict -qoptimize=3 -qmaxmem=8192"
+export CFLAGS="-I /usr/local/include"
+export LDFLAGS="-L /usr/local/lib"
+export CPPFLAGS=$CFLAGS
+export CXXFLAGS=$CFLAGS
+
+./configure --prefix=/usr/local \
+                --localstatedir=/var/mysql \
+                --sbindir='/usr/local/bin' \
+                --libexecdir='/usr/local/bin' \
+                --enable-thread-safe-client \
+                --enable-large-files
+</programlisting>
+
+        <para>
+          The preceding options are used to compile the MySQL
+          distribution that can be found at
+          <ulink url="http://www-frec.bull.com/"/>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you change the <option>-O3</option> to <option>-O2</option>
+          in the preceding <command>configure</command> line, you must
+          also remove the <option>-qstrict</option> option. This is a
+          limitation in the IBM C compiler.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you are using <command>gcc</command> to compile MySQL, you
+          <emphasis>must</emphasis> use the
+          <option>-fno-exceptions</option> flag, because the exception
+          handling in <command>gcc</command> is not thread-safe. There
+          are also some known problems with IBM's assembler that may
+          cause it to generate bad code when used with
+          <command>gcc</command>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you have problems with signals (MySQL dies unexpectedly
+          under high load), you may have found an OS bug with threads
+          and signals. In this case, you can tell MySQL not to use
+          signals by configuring as follows:
+        </para>
+
+<programlisting>
+CFLAGS=-DDONT_USE_THR_ALARM CXX=gcc \
+CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti \
+-DDONT_USE_THR_ALARM" \
+./configure --prefix=/usr/local/mysql --with-debug \
+    --with-low-memory
+</programlisting>
+
+        <para>
+          This does not affect the performance of MySQL, but has the
+          side effect that you cannot kill clients that are
+          <quote>sleeping</quote> on a connection with
+          <command>mysqladmin kill</command> or <command>mysqladmin
+          shutdown</command>. Instead, the client dies when it issues
+          its next command.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          On some versions of AIX, linking with
+          <literal>libbind.a</literal> makes
+          <literal>getservbyname()</literal> dump core. This is an AIX
+          bug and should be reported to IBM.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
+  <section id="hpux-installation-source">
+
+    <title>Notes on Installing MySQL on HP-UX from Source</title>
+
+    <para>
+      Additional notes on compiling MySQL on HP-UX.
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          If you are using HP-UX compiler, you can use the following
+          command (which has been tested with <command>cc</command>
+          B.11.11.04):
+        </para>
+
+<programlisting>
+CC=cc CXX=aCC CFLAGS=+DD64 CXXFLAGS=+DD64 ./configure \
+    --with-extra-character-set=complex
+</programlisting>
+
+        <para>
+          You can ignore any errors of the following type:
+        </para>
+
+<programlisting>
+aCC: warning 901: unknown option: `-3': use +help for online
+documentation
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          If you get the following error from
+          <command>configure</command>, verify that you do not have the
+          path to the K&amp;R compiler before the path to the HP-UX C
+          and C++ compiler:
+        </para>
+
+<programlisting>
+checking for cc option to accept ANSI C... no
+configure: error: MySQL requires an ANSI C compiler (and a C++ compiler).
+Try gcc. See the Installation chapter in the Reference Manual.
+</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>
+          Another reason for not being able to compile is that you did
+          not define the <literal>+DD64</literal> flags as just
+          described.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
 </section>


Thread
svn commit - mysqldoc@docsrva: r23788 - in trunk: . refman-5.1 refman-5.5 refman-5.6paul.dubois16 Nov