Hi!
>>>>> "Michael" == Michael Stassen <[EMAIL PROTECTED]> writes: <cut> >> This is strange; I have built mysqlbinlog on HPUX 10.x and many other OS >> without having to add -lpthread (or similar) to the link line. >> >> Here is the link line on our HPUX 10.20 machine: >> >> /bin/sh ../libtool --mode=link gcc -O3 -DDBUG_OFF -DHPUX >> -I/opt/dce/include -felide-constructors -fno-exceptions -fno-rtti -O3 >> -fno-implicit-templates -fno-exceptions -fno-rtti >> -DHAVE_BROKEN_SNPRINTF -D_INCLUDE_LONGLONG -DSIGNALS_DONT_BREAK_READ >> -DDO_NOT_REMOVE_THREAD_WRAPPERS -DHPUX -DSIGNAL_WITH_VIO_CLOSE -o >> mysqlbinlog mysqlbinlog.o ../libmysql/libmysqlclient.la -lcrypt -lm >> gcc -O3 -DDBUG_OFF -DHPUX -I/opt/dce/include -felide-constructors >> -fno-exceptions -fno-rtti -O3 -fno-implicit-templates -fno-exceptions >> -fno-rtti -DHAVE_BROKEN_SNPRINTF -D_INCLUDE_LONGLONG >> -DSIGNALS_DONT_BREAK_READ -DDO_NOT_REMOVE_THREAD_WRAPPERS -DHPUX >> -DSIGNAL_WITH_VIO_CLOSE -o mysqlbinlog mysqlbinlog.o >> ../libmysql/.libs/libmysqlclient.a -lcrypt -lm -lcrypt -lm >> >> No problem here... Michael> I see only two differences: You have -DDO_NOT_REMOVE_THREAD_WRAPPERS and Michael> -DSIGNAL_WITH_VIO_CLOSE which I do not. Should I? I looked at configure Michael> (in 3.23.46). It only sets DO_NOT_REMOVE_THREAD_WRAPPERS if it thinks you Michael> are running rhapsody, and it only sets SIGNAL_WITH_VIO_CLOSE if it thinks Michael> you're running darwin. Should these be added to hpux10.20? These are now options in MySQL 4.0.1 (they are automaticly added to the link line); These should however not affect if libpthread is used or not for mysqlbinlog. Michael> Actually, while looking at configure, I see that for HPUX 10.20 it does: Michael> *hpux10.20*) Michael> echo "Enabling snprintf workaround for hpux 10.20" Michael> CFLAGS="$CFLAGS -DHAVE_BROKEN_SNPRINTF -DSIGNALS_DONT_BREAK_READ" Michael> CXXFLAGS="$CXXFLAGS -DHAVE_BROKEN_SNPRINTF -D_INCLUDE_LONGLONG -DSIGNALS_DONT_BREAK_READ" Michael> if test "$with_named_thread" = "no" Michael> then Michael> echo "Using --with-named-thread=-lpthread" Michael> with_named_thread="-lcma" Michael> fi Michael> ;; Michael> I've been building with "--with-named-thread-libs=-ldce" per the Michael> manual. Is that a mistake? No, this is what I also use. Here is the exact link line I use for our binaries, that compile without any problem: CFLAGS="-DHPUX -I/opt/dce/include -O3" CXX=gcc CXXFLAGS="-DHPUX -I/opt/dce/include -felide-constructors -fno-exceptions -fno-rtti -O3 " ./configure --prefix=/usr/local/mysql "--with-comment=Official MySQL binary" --with-extra-charsets=complex "--with-server-suffix=" --enable-thread-safe-client --with-pthread --with-named-thread-libs=-ldce --with-lib-ccflags=-fpic --disable-shared Michael> <CUT> Michael> 4) Test rpl000001 fails immediately because: >> >> >> The file '../../std_data/words.dat' must be in the database directory >> >> or be readable by all >> Michael> Clearly, configure/make should have made std_data/words.dat readable by all. >> >> I checked our distribution: >> >> monty@mysql-work$ gtar tvfz binary/mysql-4.0.1-alpha.tar.gz | grep words.dat >> -rw-r--r-- 102/234 81 2001-12-20 06:03:01 >mysql-4.0.1-alpha/mysql-test/std_data/words.dat >> >> Looks ok to me. Michael> What's your UMASK? Mine is 077. So while words.dat is world-readable Michael> in the archive, it is not world-readable once extracted. And to be clear, Michael> I'm talking about source, not binary. The above is our source distribution. Anyway, mysql-test-run is meant to be run by the developer after compiling MySQL, not by the end user... Regards, Monty --------------------------------------------------------------------- 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
