retitle 383759 libmysqlclient15off needs at least pentium cpu
tags 383759 + confirmed wontfix upstream
forwarded 383759 http://bugs.mysql.com/bug.php?id=21765
stop
Hello Yavor
Thanks a lot for your work on the backtraces, I guess the last one cleared
the issue:
On 2006-08-21 Yavor Doganov wrote:
> Program received signal SIGILL, Illegal instruction.
> [Switching to Thread -1486767808 (LWP 25270)]
> 0xa7c4dbb0 in CpuId (input=0, output=0xafd6ab60) at integer.cpp:1025
On that line in extras/yassl/taocrypt/src/integer.cpp the following source
code is found:
static void CpuId(word32 input, word32 *output)
{
#ifdef __GNUC__
__asm__
(
// save ebx in case -fPIC is being used
"push %%ebx; cpuid; mov %%ebx, %%edi; pop %%ebx"
: "=a" (output[0]), "=D" (output[1]), "=c" (output[2]),
"=d"(output[3])
: "a" (input)
);
#else
The "cpuid" instruction was not fully implemented in early Cyrix CPUs
though (I was already wondering why your /proc/cpuinfo says "model name: 486"
even your cpu was supposed to be a Pentium clone..).
http://www.pcguide.com/ref/cpu/fam/g5C6x86-c.html says:
"Processor Identification Problems: In addition to programs that won't work
with the 6x86, there are those that would work with the 6x86 if only they
knew what it was. There is a special instruction called "CPUID" that is used
to identify the make and model of the processor. Some programs use this to
detect if the computer is running on a Pentium, and will refuse to run (or
run in a reduced mode) if they don't find one. These tests were originally
used by software requiring a lot of power, to distinguish between Pentiums
and 486s (which the software would be too slow to run on). The 6x86 by
default does not respond to the "CPUID" instruction so some programs think
it is a 486."
So in the end you might hope that MySQL do a work around for the Cyrix or
i486 in general but I would not be so optimistic about it which I tagged
the bug report as "wontfix" until I get better news :)
bye,
-christian-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
