From: Adrian Bunk <bunk@stusta.de>
To: "Pedro Mullor Jiménez" <pmullor@skynet.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9 won't compile
Date: Fri, 6 Apr 2007 18:40:58 +0200 [thread overview]
Message-ID: <20070406164058.GK29169@stusta.de> (raw)
In-Reply-To: <1175855823.16114.12.camel@localhost>
On Fri, Apr 06, 2007 at 12:37:03PM +0200, Pedro Mullor Jiménez wrote:
> Dear all,
>
> I downloaded version 2.6.9 of the kernel from kernel.org
> I went throught menuconfig, importing the configuration of my current
> 2.6.15-28-686.
>
> I then tried to compile it but the compilation exits with an error
> (below).
>
> I also tried to do make mrproper, got rid of the .config file, made
> menuconfig again without importing anything, and when compiling it
> failed again.
>
> The reason for me to use this kernel is because I have a VIA VT82C
> 693A/598/686 chipset and I suffer from perf problems (which google says
> only happen since 2.6.10).
Can you give a pointer or description of this problem?
The preferred solution for you would not be to run an ancient kernel
with tons of known security holes but to get this problem fixed.
> Might I request to be personally CC'ed in the answers/comments posted in
> response to this post ?
>
> Many thanks in advance for your comments and help!
>
> With kind regards,
> Pedro Mullor
>
>
> CHK include/linux/version.h
> make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
> 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
> {standard input}: Assembler messages:
> {standard input}:813: Error: suffix or operands invalid for `mov'
> {standard input}:814: Error: suffix or operands invalid for `mov'
> {standard input}:1040: Error: suffix or operands invalid for `mov'
> {standard input}:1041: Error: suffix or operands invalid for `mov'
> {standard input}:1121: Error: suffix or operands invalid for `mov'
> {standard input}:1122: Error: suffix or operands invalid for `mov'
> {standard input}:1226: Error: suffix or operands invalid for `mov'
> {standard input}:1227: Error: suffix or operands invalid for `mov'
> {standard input}:1290: Error: suffix or operands invalid for `mov'
> {standard input}:1302: Error: suffix or operands invalid for `mov'
> make[1]: *** [arch/i386/kernel/process.o] Error 1
> make: *** [arch/i386/kernel] Error 2
Older kernels use an assembler syntax no longer supported by recent
binutils.
A patch is at [1].
cu
Adrian
[1] http://www.kernel.org/pub/linux/devel/binutils/linux-2.6-seg-5.patch
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-04-06 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 10:37 2.6.9 won't compile Pedro Mullor Jiménez
2007-04-06 13:24 ` Benoit Boissinot
2007-04-06 16:40 ` Adrian Bunk [this message]
2007-04-06 23:17 ` Pedro Mullor Jiménez
[not found] <fa.wFTrjBlmoNpWJlHvvdovpz3pV2I@ifi.uio.no>
2007-04-06 15:52 ` Robert Hancock
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=20070406164058.GK29169@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmullor@skynet.be \
/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