Entry

How can I compile and run MySQL under Tru64 4.0D?

Feb 8th, 2000 05:56
Nathan Wallace, Ann Cantelow

I've had some success with compiling installing mysql 3.22.30 on
DU/Tru64 version 4.0D machine and I thought I'd share my configure
string in case anyone else has similar problems that I have had.

My main problem was mostly only putting together in my head the various
information tip in the manual and archives of this list, so it's just
about all my own fault I had difficulties.  ;-)

This configure string did it for me:

-----------
env CC="cc -pthread" CFLAGS="-I./include -DDONT_USE_THR_ALARM" CXX=gcc \
  CXXFLAGS="-O3 -DDONT_USE_THR_ALARM" ./configure --with-low-memory  \
  --with-named-thread-libs="-lpthread -lmach -lexc"
----------

The -DDONT_USE_THR_ALARM may not be necessary.  I had it there to try to
solve problems with connections which was solved in another way, see
below.  You might not need --with-low-memory either, not sure.

The trickiest part I found:

In the manual there is mention of a problem with _exit undefined errors
and a suggestion that the 4.0D ld is broken and we should use an old ld
program copied in from 4.0C.  An easier and less nerve-wracking solution
is to use --with-named-thread-libs "-lpthread -lmach -lexc" instead of
the manual-suggested "-lpthread -lmach -lexc -lc".  Dropping -lc out of
the list eliminates some confusion that happens somewhere in there
causing well-known functions from lc like _exit to get lost in the
shuffle.

I originally compiled with gcc version 2.8.1.  The compile went fine but
there were lots of run-time problems with lost connections, and the
fork_test.pl and fork2_test.pl test scripts would only succeed with 1 or
2 iterations instead of the originally configured 10000, and then only
half the time.

In the archives of this list from August there is an instruction to
upgrade gcc to the latest version.  This solved our problems with lost
connections!  Thanks heaps to Mr. Widenius for that answer and for
working that all out!  I upgraded to gcc 2.95.2, and also upgraded mysql
from 3.22.27 to 3.22.30, and fork_test.pl and fork2_test.pl now run for
10000 interations without any problems.  As somebody else said in the
archives, I'm a happy puppy.

The server has been up with no errors or restarts since I first started
it yesterday.  Our usage is usually light with occasional surges of a
moderate number of queries.  So far things are great. :)