Oracle 5.0 Reference Manual page 194

./configure --prefix=/usr/local \
--localstatedir=/var/mysql \
--sbindir='/usr/local/bin' \
--libexecdir='/usr/local/bin' \
--enable-thread-safe-client \
--enable-large-files
The preceding options are used to compile the MySQL distribution that can be found at
frec.bull.com/.
If you change the
-O3
option. This is a limitation in the IBM C compiler.
If you are using to compile MySQL, you must use the
gcc
exception handling in
gcc
assembler that may cause it to generate bad code when used with gcc.
Use the following
configure
CC="gcc -pipe -mcpu=power -Wa,-many" \
CXX="gcc -pipe -mcpu=power -Wa,-many" \
CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti" \
./configure --prefix=/usr/local/mysql --with-low-memory
The option is necessary for the compile to be successful. IBM is aware of this problem
-Wa,-many
but is in no hurry to fix it because of the workaround that is available. We do not know if the
is required with
exceptions
generates faster code, you should always use it with gcc.
If you get a problem with assembler code, try changing the
Typically power2, power, or
or 604e. We are not positive but suspect that
power2 machine.
If you do not know what your CPU is, execute a
like 000514676700, with a format of
unique system ID and
www16.boulder.ibm.com/pseries/en_US/cmds/aixcmds5/uname.htm.
This gives you a machine type and a machine model you can use to determine what type of CPU you
have.
If you have problems with threads on AIX 5.3, you should upgrade AIX 5.3 to technology level 7
(5300-07).
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:
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
This doesn't affect the performance of MySQL, but has the side effect that you can't kill clients that are
"sleeping" on a connection with
dies when it issues its next command.
On some versions of AIX, linking with
AIX bug and should be reported to IBM.
For AIX 4.2.1 and gcc, you have to make the following changes.
Other Unix Notes
to in the preceding
-O2
is not thread-safe! There are also some known problems with IBM's
line with 2.95 on AIX:
gcc
2.95, but because MySQL doesn't use exceptions and the option
gcc
may need to be used. Alternatively, you might need to use
powerpc
xxyyyyyymmss
is the ID of the CPU Planar. A chart of these values can be found at
mm
mysqladmin kill
libbind.a
174
line, you must also remove the
configure
-fno-exceptions
-mcpu=xxx
would likely be safe most of the time, even on a
power
command. It produces a string that looks
uname -m
where and
xx
or
mysqladmin
makes
getservbyname()
http://www-
-qstrict
flag, because the
option to match your CPU.
are always 00,
ss yyyyyy
shutdown. Instead, the client
dump core. This is an
-fno-
604
is a
http://