From: Baruch Even <baruch@ev-en.org>
To: Huess <huexxx@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Error compiling linux-2.6.9
Date: Sat, 17 Dec 2005 17:48:15 +0000 [thread overview]
Message-ID: <43A44F5F.7020207@ev-en.org> (raw)
In-Reply-To: <be2547710512151915k3ff5ba78j@mail.gmail.com>
Huess wrote:
> [1.] Error compiling linux-2.6.9
> [2.] When I try to compile the kernel, executing make, the script
> returns an error.
> [3.]
> [4.] Linux version 2.6.13-15-smp (geeko@buildhost) (gcc version 4.0.2
> 20050901 (prerelease) (SUSE Linux)) #1 SMP Tue Sep 13 14:56:15 UTC
> 2005
> [5.]
> [6.] Running make, I obtain the following:
> piv2800ht:/usr/src/linux-2.6.9 # make vmlinux
> CHK include/linux/version.h
> make[1]: `arch/i386/kernel/asm-offsets.s' está actualizado.
> CHK include/linux/compile.h
>
> CC arch/i386/kernel/process.o
> arch/i386/kernel/process.c: In function 'show_regs':
> arch/i386/kernel/process.c:252: warning: pointer targets in passing
> argument 2 of 'show_trace' differ in signedness
> {entrada estándar}: Mensajes del ensamblador:
>
> {entrada estándar}:741: Error: sufijo u operandos inválidos para `mov'
> {entrada estándar}:742: Error: sufijo u operandos inválidos para `mov'
> {entrada estándar}:950: Error: sufijo u operandos inválidos para `mov'
>
> {entrada estándar}:951: Error: sufijo u operandos inválidos para `mov'
> {entrada estándar}:1027: Error: sufijo u operandos inválidos para `mov'
> {entrada estándar}:1028: Error: sufijo u operandos inválidos para `mov'
>
> {entrada estándar}:1125: Error: sufijo u operandos inválidos para `mov'
> {entrada estándar}:1126: Error: sufijo u operandos inválidos para `mov'
> {entrada estándar}:1220: Error: sufijo u operandos inválidos para `mov'
>
> {entrada estándar}:1232: Error: sufijo u operandos inválidos para `mov'
> make[1]: *** [arch/i386/kernel/process.o] Error 1
> make: *** [arch/i386/kernel] Error 2
Use http://www.google.ie/search?hl=en&q=linux-2.6-seg-5.patch to search
for the patch I used to solve a similar problem.
As Adrian said, the newer binutils are more strict on what they accept.
Baruch
prev parent reply other threads:[~2005-12-17 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <be2547710512151912w1593ff4eh@mail.gmail.com>
2005-12-16 3:15 ` PROBLEM: Error compiling linux-2.6.9 Huess
2005-12-16 19:09 ` Adrian Bunk
2005-12-17 17:48 ` Baruch Even [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=43A44F5F.7020207@ev-en.org \
--to=baruch@ev-en.org \
--cc=huexxx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.