-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jonathan A. wrote:
> On Sun, 01 May 2005 00:09:07 +0200, Julius Schwartzenberg
> <usenet@zgod.cjb.net> appears to have said:
>
>
>>Grant Coady wrote:
>>
>>>Recompile kernel to suit CPU, the IBM/Cyrix is not a 686, so
>>>generic 586 CPU would seem safer.
>>
>>I'm using the default Slackware 10.1 kernel (version 2.4.29). I thought
>>(and according to the config in /boot) this one is compiled for 486.
>>Isn't this the case?
>
>
> I believe so. I'm still running 10.0, but I sure haven't heard anything
> about a move to i586 for the default kernels.
>
> Hopefully, someone more knowledgeable than I will come along with a real
> explanation, but I'll have a go at this. I found an interesting thread
> about uname and machine information here:
>
> http://lists.ssc.com/pipermail/linux-list/2000-June.txt
>
> (The thread's a little way down, just search for "uname")
>
> I have a similar situation. I run an Athlon-XP 2600+, and my kernel is
> compiled for K7 architecture, yet "uname -m" reports "i686".
>
> It's simple enough to get *most* software (especially the stuff that
> uses autoconf) to build for the correct architecture by setting the
> environment variables CFLAGS and CXXFLAGS.
>
> For instance, among other variables for gcc and friends, I have:
>
> export CFLAGS="-march=athlon-xp"
> export CXXFLAGS="-march=athlon-xp"
>
> in my ~/.bash_profile
>
> That keeps it straight for most compilations. There are some packages
> out there that actually use `uname -m` to get the machine type, though.
> They require a little hand editing of makefiles, or some such, if you're
> really determined to have the march set for your architecture. In my
> case, it's only to get a little extra optimization... in your case it
> looks to be critical.
>
> The CFLAGS thing is a workaround, rather than a solution but, judging by
> the thread at the link above, it might be the only way around it, short
> of hacking the kernel code.
>
> HTH,
> Jonathan
>
On that note,. I have a K6-2 and it shows a i586, go figure.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCc8QeSmxUFLwQOoMRAh1yAKCXWd9KjfC1u1nUlrFyld 2ggVJ/IwCgrP5/
PFtxUPijGEP+yBUMYqoO8SE=
=brcX
-----END PGP SIGNATURE-----