From: "David L. Nicol" <david@kasey.umkc.edu>
To: linux-kernel@vger.kernel.org, chris.ricker@genetics.utah.edu
Subject: "no such 386 instruction" with gcc 2.95.2
Date: Thu, 25 Jan 2001 15:46:48 -0600 [thread overview]
Message-ID: <3A709EC8.72C3F911@kasey.umkc.edu> (raw)
I think I must need to upgrade my assembler, but:
2.4.0/Documentation/Changes does not list an assembler version.
make[2]: Entering directory `/mnt/sdb2/src/linux-2.4.0/drivers/md'
gcc -D__KERNEL__ -I/mnt/sdb2/src/linux-2.4.0/include -Wall -Wstrict-proto
types -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-sta
ck-boundary=2 -march=i586 -DMODULE -DMODVERSIONS -include /mnt/sdb2/src/l
inux-2.4.0/include/linux/modversions.h -DEXPORT_SYMTAB -c xor.c
{standard input}: Assembler messages:
{standard input}:996: Error: no such 386 instruction: `movups'
{standard input}:997: Error: no such 386 instruction: `movups'
{standard input}:998: Error: no such 386 instruction: `movups'
{standard input}:999: Error: no such 386 instruction: `movups'
{standard input}:1001: Error: no such 386 instruction: `prefetcht0'
{standard input}:1002: Error: no such 386 instruction: `prefetcht0'
{standard input}:1005: Error: no such 386 instruction: `movaps'
{sta...
...
--
David Nicol 816.235.1187 dnicol@cstp.umkc.edu
Five seconds of light is a lot of data.
-
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/
next reply other threads:[~2001-01-25 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 21:46 David L. Nicol [this message]
2001-01-25 21:51 ` "no such 386 instruction" with gcc 2.95.2 Brian Gerst
2001-01-27 10:17 ` Pavel Machek
2001-01-28 15:23 ` Matti Aarnio
2001-01-27 15:05 ` Jakob Schroeter
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=3A709EC8.72C3F911@kasey.umkc.edu \
--to=david@kasey.umkc.edu \
--cc=chris.ricker@genetics.utah.edu \
--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