At 15:58 -0600 3/15/03, Mike Blezien wrote:
Hello all,
we will be upgrading our current MySQL version 3.23.40 to 3.23.55,
compiled from source. We've always had good luck on our machine
compiling from the source as opposed to using binaries.
my question is, I was told, that using the
"--enable-thread-safe-client" when compiling was a good idea. I was
wondering, if infact this is recommended.
Depends. Are you going to be writing multi-threaded client programs?
If not, you don't need it.
When you were told that using this option was a good idea, what reason
were you given for using it?
We are on a RH/Linux 6.2 We compile with the 2.91 gcc with no
problems, with the last two sources we compiled.
We use the following configuration when we compile:
CCFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors
-fno-exceptions -fno-rtti" \
./configure --prefix=/var/lib --with-berkeley-db --without-docs
--without-bench \
--without-readline --enable-assembler --with-mysqld-ldflags=-all-static \
--with-mysqld-user=mysql --with-low-memory --with-tcp-port=3306 \
--with-unix-socket=/tmp/mysql.sock --localstatedir=/var/lib/mysql
appreciate any input on using the ""--enable-thread-safe-client" or
if it's really needed in our case.
TIA ;)
--
Paul DuBois
http://www.kitebird.com/
sql, query
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
