On Sat, Aug 19, 2006 at 05:47:57PM +0200, Christian Hammers wrote: > The last functions in the backtrace belong to the rather new SSL code > which has been activated in 5.0.22-4 so it is indeed be likely that the > problem "suddenly" appears after the last update.
That's true, this is the problem. I tried to build the package (5.0.22-4) from the Debian source on that machine, but it fails to build: if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I../ndb/include -I../ndb/include/ndbapi -I../ndb/include/mgmapi -I../sql -DDBUG_OFF -DBIG_JOINS=1 -O2 -MT resolveip.o -MD -MP -MF ".deps/resolveip.Tpo" -c -o resolveip.o resolveip.c; \ then mv -f ".deps/resolveip.Tpo" ".deps/resolveip.Po"; else rm -f ".deps/resolveip.Tpo"; exit 1; fi /bin/sh ../libtool --preserve-dup-deps --tag=CC --mode=link gcc -DDBUG_OFF -DBIG_JOINS=1 -O2 -rdynamic -o resolveip resolveip.o ../mysys/libmysys.a ../dbug/libdbug.a ../strings/libmystrings.a -lpthread -lcrypt -lnsl -lm -lpthread gcc -DDBUG_OFF -DBIG_JOINS=1 -O2 -rdynamic -o resolveip resolveip.o ../mysys/libmysys.a ../dbug/libdbug.a ../strings/libmystrings.a -lpthread -lcrypt -lnsl -lm -lpthread collect2: ld returned 1 exit status make[5]: *** [resolveip] Error 1 make[5]: Leaving directory `/home/disorder/src/mysql-dfsg-5.0-5.0.22/extra' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/disorder/src/mysql-dfsg-5.0-5.0.22/extra' make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/disorder/src/mysql-dfsg-5.0-5.0.22/extra' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/disorder/src/mysql-dfsg-5.0-5.0.22' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/disorder/src/mysql-dfsg-5.0-5.0.22' make: *** [build-stamp] Error 2 > (quick fix: manually install 5.0.22-3 again, it might still be in > /var/cache/apt/archives) It works with 5.0.22-3 from snapshot.debian.net and the exim4 packages configure and work fine. So perhaps this bug should be reassigned to libmysqlclient15off? > I checked the build log[1] and it says that the > (libmysqlclient15off_5.0.24-1) package was tried to get compiled for the > i486-linux-gnu target. > Sadly the further g++ calls in the build log do not seem to have a --target= > paramter so I cannot tell for sure what GCC actually did. Could be a GCC-related issue, that's why I tried to build it, but unfortunately failed. > The 100 MHz Cyrix CPU was a Pentium clone i.e. at least no pre-i486 CPU, > right? Yes, it is a Pentium clone that should be equivalent to Pentium 120 MHz. $ cat /proc/cpuinfo processor : 0 vendor_id : unknown cpu family : 4 model : 0 model name : 486 stepping : unknown fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : no cpuid level : -1 wp : yes flags : bogomips : 98.81 It's not really a Cyrix, but ST (the Canadian company that had a license to produce them once upon a time). AFAIK, it is 100% equal to the original Cyrix. > Please try if the official MySQL i386 version works better. Download > "Linux (non RPM, Intel C/C++ compiled, glibc-2.3) downloads > Linux (x86) Standard 5.0.24 26.0M Download" > from http://dev.mysql.com/downloads/mysql/5.0.html, unpack it and just > copy the libmysqlclient.so.15.0.0 over to /usr/lib/ I downloaded it, but there is no such file there. I can give anyone (DD or not, nevermind) an account with sudo rights to reproduce/debug this. -- Best regards / SSC Varna | E-mail: [EMAIL PROTECTED] Yavor Doganov | Mobile: +359 88 7517748 Southway Shipping Consultancy Ltd.-Gibraltar, Varna Branch Ph: +359 52 600129, 600130, 603643 | Fax: +359 52 603612 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]