public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cliff Albert <cliff@oisec.net>
To: Steve Kieu <haiquy@yahoo.com>
Cc: kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4 broken on 486SX
Date: Sat, 25 Aug 2001 09:12:26 +0200	[thread overview]
Message-ID: <20010825091226.A18300@oisec.net> (raw)
In-Reply-To: <3B86BAF0.489E92C6@didntduck.org> <20010825024627.30130.qmail@web10404.mail.yahoo.com>
In-Reply-To: <20010825024627.30130.qmail@web10404.mail.yahoo.com>

On Sat, Aug 25, 2001 at 12:46:27PM +1000, Steve Kieu wrote:

> By the way, I got this strange thing too but with
> 2.2.19. I got the kernel 2.2.19 source from slackware
> site, compile it using gcc 2.95.3 and select CPU as
> 486, but the compiled image can not run in my 486 CPU
> (it does run fine in the machine I compile it i686).
> There is no way. Ironically 2.4.x works for me, if I
> choose 486, I can run it on 486. 
> 
> I noticed the differrence in the cflags in 2.2.19 it
> is like  -m486 -DCPU=i486  and in 2.4.x it is
> -march=i486 instead of -DCPU=i486. According to gcc
> documentation it is the same. Why it is like that ? 

Linux 2.4.8-ac3 runs just fine on my Compaq Prosignia VS (which has a 486DX66)

-- 
Cliff Albert		| RIPE:	     CA3348-RIPE | www.oisec.net
cliff@oisec.net		| 6BONE:     CA2-6BONE	 | icq 18461740

      reply	other threads:[~2001-08-25  7:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-24 19:42 2.4 broken on 486SX Ross Vandegrift
2001-08-24 19:59 ` Richard B. Johnson
2001-08-24 20:17 ` Ross Vandegrift
2001-08-24 20:37   ` Brian Gerst
2001-08-25  2:46     ` Steve Kieu
2001-08-25  7:12       ` Cliff Albert [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010825091226.A18300@oisec.net \
    --to=cliff@oisec.net \
    --cc=haiquy@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox