I managed to come up with a much simpler solution and hence a much
simpler patch, which is not linux specific and does not require /proc or
any other file parsing.
It turns out the upstream fix to mysql was on the right track, but must
have been working on a BSD system or at least something
I have a 486 DX2/66 (no cpuid instruction), which also get and illegal
instruction whenever anything tries to use the mysql libraries. In my
case I saw it when trying to start proftpd after upgrading from sarge to
etch. If I comment out the mysql modules in the proftpd config, the
problem goes
On Wed, Apr 04, 2007 at 05:48:22PM -0400, Lennart Sorensen wrote:
I have a 486 DX2/66 (no cpuid instruction), which also get and illegal
instruction whenever anything tries to use the mysql libraries. In my
case I saw it when trying to start proftpd after upgrading from sarge to
etch. If I
I looked at the cpuid code in yassl, and while it tries to safely check
for the cpuid instruction first, it does it in a broken way.
it currently sets up a signal handler to catch the illegal instruction
if it isn't supported, by using signal(), but unfortunately that is not
supported in
Here is a patch that makes mysql run on my 486 without disabling use of
MMX, and such on other systems.
It isn't great yet, since it should really have some ifdef's for linux
only since it requires the linux specific /proc/cpuinfo, which of course
implies it requires /proc to be mounted. On the
5 matches
Mail list logo
