found 512623 5.0.32-7etch8
retitle 512623 Mysql fails with illegal instruction error on a 486
thanks
model name : 486
That probablly explains it, I suspect mysqls build process is
incorrectly building binaries that will only work on a pentium or
higher. Some upstream build systems have a nasty habbit of overriding
distro compiler configurations and doing things there own way and there
are so few 486 users left this often doesn't get spotted until it's too
late.
You might want to try a local rebuild to see if that builds a binary
that will run on your system.
Given the point that etch is at in it's release cycle I think this is
very unlikely to be fixed in etch. If you plan to continue using debian
on 486 based machines I would suggest you start testing lenny on one now
looking out for this bug and similar ones before it becomes stable and
therefore too late for anything much to get done about such issues.
>I'm sorry, I thought all this information would be provided by Report
Bug, which I used to
file this bug report.
reportbug normally does provide that information, maybe there was
something odd in your setup.
(quoting full mail below since axst didn't post it to the bug report)
a...@users.sourceforge.net wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
$ uname -a
Linux notker 2.6.23.1 #2 Sun Oct 21 09:06:35 CEST 2007 i486 GNU/Linux
$ 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 : 19.81
clflush size : 32
$ dpkg -l mysql\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name Version Description
+++-============================-============================-========================================================================
un mysql <none> (no
description available)
un mysql-base <none> (no
description available)
ii mysql-client 5.0.32-7etch8 mysql
database client (meta package depending on the latest version)
pn mysql-client-4.1 <none> (no
description available)
ii mysql-client-5.0 5.0.32-7etch8 mysql
database client binaries
ii mysql-common 5.0.32-7etch8 mysql
database common files (e.g. /etc/mysql/my.cnf)
rc mysql-common-4.1 4.1.11a-4sarge7 mysql
database common files (e.g. /etc/mysql/my.cnf)
un mysql-dev <none> (no
description available)
un mysql-devel <none> (no
description available)
un mysql-doc <none> (no
description available)
un mysql-doc-4.1 <none> (no
description available)
un mysql-gpl-client <none> (no
description available)
un mysql-gpl-dev <none> (no
description available)
un mysql-gpl-doc <none> (no
description available)
un mysql-manual <none> (no
description available)
un mysql-server <none> (no
description available)
$ mysql
Illegal instruction
I'm sorry, I thought all this information would be provided by Report
Bug, which I used to
file this bug report.
On Thu, 22 Jan 2009, peter green wrote:
Starting "mysql" from the command line always results in "Illegal
Instruction", then execution terminates (of course). The parameters
seem not to change anything. The situation is the same with
"mysqldump".
What CPU and what kernel are you using on the problem machine?
What version of the mysql-client package are you using?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFJekMoMiDYPOQNapERAoRzAJsFyVK0/vvUXSmQxR4Kr9ETDnc4ogCg2vGM
3K0JyCxcJYxXuKvF6MEJGlw=
=V7G7
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
