All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Dittmer <jdittmer@ppp0.net>
To: Christian Zankel <chris@zankel.net>
Cc: czankel@tensilica.com, Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: arch xtensa does not compile
Date: Sun, 10 Jul 2005 13:12:03 +0200	[thread overview]
Message-ID: <42D10283.6040701@ppp0.net> (raw)
In-Reply-To: <42D0990D.8030701@zankel.net>

Christian Zankel wrote:
> Jan Dittmer wrote:
> 
>>I guess I'm using the wrong binutils version (2.15.94.0.2.2). Which is the
>>recommended gcc/binutils pair which is supposed to compile the kernel?
> 
> 
> Bob Wilson made some changes to binutils last week to address this 
> problem but he only submitted it to the latest binutils version.
> 
> With the latest gcc+binutils toolchain, the kernel compiles for me.
> Note, however, that I just submitted a patch that is not in Linus' tree, 
> yet.
> 
> gcc version 3.4.5 20050707 (prerelease)
> GNU ld version 2.16.91 20050707

Yep, using GNU ld 20050710 and gcc 3.4.4 20050513 I get much further now.

  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
arch/xtensa/kernel/built-in.o: In function `__down_interruptible':
: dangerous relocation: l32r: literal target out of range: .sched.literal
arch/xtensa/kernel/built-in.o: In function `__down_interruptible':
: dangerous relocation: l32r: literal target out of range: (.sched.literal+0x4)
arch/xtensa/kernel/built-in.o: In function `__down_interruptible':
: dangerous relocation: l32r: literal target out of range: (.sched.literal+0x8)
arch/xtensa/kernel/built-in.o: In function `__down_interruptible':
: dangerous relocation: l32r: literal target out of range: (.sched.literal+0xc)
arch/xtensa/kernel/built-in.o: In function `__down_interruptible':
: dangerous relocation: l32r: literal target out of range: (.sched.literal+0xc)
arch/xtensa/kernel/built-in.o: In function `__down':
: dangerous relocation: l32r: literal target out of range: .sched.literal
arch/xtensa/kernel/built-in.o: In function `__down':
: dangerous relocation: l32r: literal target out of range: (.sched.literal+0x4)
arch/xtensa/kernel/built-in.o: In function `__down':
: dangerous relocation: l32r: literal target out of range: (.sched.literal+0x8)
arch/xtensa/kernel/built-in.o: In function `__down':
: dangerous relocation: l32r: literal target out of range: (.sched.literal+0xc)
kernel/built-in.o: In function `schedule':

... lots more of these, until ...

rwsem.c:(.sched.text+0x290): dangerous relocation: l32r: literal target out of range: (. sched.literal+0x18)
rwsem.c:(.sched.text+0x297): dangerous relocation: l32r: literal target out of range: (. sched.literal+0x1c)
rwsem.c:(.sched.text+0x29c): dangerous relocation: l32r: literal target out of range: (. sched.literal+0x20)
rwsem.c:(.sched.text+0x2bb): dangerous relocation: l32r: literal target out of range: (. sched.literal+0x24)
make: *** [.tmp_vmlinux1] Error 1

Is the gcc version still too old? Or do I need some special config option?

Reading specs from /usr/cc/xtensa/lib/gcc/xtensa-linux/3.4.4/specs
Configured with: ../configure --prefix=/usr/cc --exec-prefix=/usr/cc/xtensa --target=xtensa-linux --disable-shared --disable-werror --disable-nls
--disable-threads --disable-werror --disable-libmudflap --with-newlib --with-gnu-as --with-gnu-ld --enable-languages=c
Thread model: single
gcc version 3.4.4 20050513 (prerelease)

Thanks,

-- 
Jan

      reply	other threads:[~2005-07-10 11:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-25 14:08 arch xtensa does not compile Jan Dittmer
2005-06-25 16:28 ` Christian Zankel
2005-07-03 15:58   ` Jan Dittmer
2005-07-04  6:51     ` Christian Zankel
2005-07-10  3:42     ` Christian Zankel
2005-07-10 11:12       ` Jan Dittmer [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=42D10283.6040701@ppp0.net \
    --to=jdittmer@ppp0.net \
    --cc=chris@zankel.net \
    --cc=czankel@tensilica.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.