public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakob Schroeter <js@camaya.de>
To: linux-kernel@vger.kernel.org
Subject: Re: "no such 386 instruction" with gcc 2.95.2
Date: Sat, 27 Jan 2001 16:05:27 +0100	[thread overview]
Message-ID: <11215119686.20010127160527@camaya.de> (raw)
In-Reply-To: <3A709EC8.72C3F911@kasey.umkc.edu>
In-Reply-To: <3A709EC8.72C3F911@kasey.umkc.edu>

Hi!

I have a similar problem when compiling recent 2.4.0-ac or 2.4.1-pre kernels:

gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe  -march=i686    -c -o i387.o i387.c
{standard input}: Assembler messages:
{standard input}:30: Error: no such 386 instruction: `ldmxcsr'
{standard input}:52: Error: no such 386 instruction: `fxsave'
{standard input}:87: Error: no such 386 instruction: `fxsave'
{standard input}:115: Error: no such 386 instruction: `fxrstor'
make[1]: *** [i387.o] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.0-ac11/arch/i386/kernel'
make: *** [_dir_arch/i386/kernel] Error 2

I'm using binutils 2.10.1 and egcs 1.1.2.

What could be the problem?

Thanks in advance,
                    Jakob


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      parent reply	other threads:[~2001-01-27 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25 21:46 "no such 386 instruction" with gcc 2.95.2 David L. Nicol
2001-01-25 21:51 ` Brian Gerst
2001-01-27 10:17 ` Pavel Machek
2001-01-28 15:23   ` Matti Aarnio
2001-01-27 15:05 ` Jakob Schroeter [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=11215119686.20010127160527@camaya.de \
    --to=js@camaya.de \
    --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