public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Antoine Zen-Ruffinen <antoine.zen@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compilation problem with kernel 2.6.9
Date: Mon, 24 Sep 2007 14:39:34 +0200	[thread overview]
Message-ID: <46F7B006.40309@gmail.com> (raw)
In-Reply-To: <2cbbd8de0709240252x34d4d66ci6bd2e20e397a7cc1@mail.gmail.com>

On 09/24/2007 11:52 AM, Antoine Zen-Ruffinen wrote:
> Hello,
> 
> I tried to compile the kernel 2.6.9 because I want to use it with
> RTLinux and that the only 2.6.x kernel supported. I used gcc 2.95.3 as
> recommended.
> But I have an error by compilation of process.c :
> 
>   CC      arch/i386/kernel/process.o
> {standard input}: Assembler messages:
> {standard input}:777: Error: suffix or operands invalid for `mov'
> {standard input}:778: Error: suffix or operands invalid for `mov'
> {standard input}:978: Error: suffix or operands invalid for `mov'
> {standard input}:979: Error: suffix or operands invalid for `mov'
> {standard input}:1051: Error: suffix or operands invalid for `mov'
> {standard input}:1052: Error: suffix or operands invalid for `mov'
> {standard input}:1161: Error: suffix or operands invalid for `mov'
> {standard input}:1162: Error: suffix or operands invalid for `mov'
> {standard input}:1172: Error: suffix or operands invalid for `mov'
> {standard input}:1184: Error: suffix or operands invalid for `mov'
> make[1]: *** [arch/i386/kernel/process.o] Error 1
> make: *** [arch/i386/kernel] Error 2
> 
> Can someone help me ?

Probably use older binutils, your gas is too new and doesn't like the input.

regards,
-- 
Jiri Slaby (jirislaby@gmail.com)
Faculty of Informatics, Masaryk University

      reply	other threads:[~2007-09-24 12:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-24  9:52 Compilation problem with kernel 2.6.9 Antoine Zen-Ruffinen
2007-09-24 12:39 ` Jiri Slaby [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=46F7B006.40309@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=antoine.zen@gmail.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