mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Satyaki Mukherjee <satyaki@tataelxsi.co.in>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: PROBLEM: Compiling Linux kernel 2.6.13.2 for Xtensa
Date: Thu, 24 Nov 2005 19:42:54 +0530	[thread overview]
Message-ID: <4385CA66.8060709@tataelxsi.co.in> (raw)

Hi,

I am facing problems while compiling the Linux kernel(version 2.6.13.2) 
for XTENSA. I am using xtensa-elf- toolchain of following versions -
binutils - 2.12.1
gcc - 3.0.4
The toolchain was built from the sources as per the instruction given 
with the patches that came along with XTENSA configuration
The configuration used for kernel compilation is --- 
arch/xtensa/configs/iss_defconfig.

The compilation seems to go fine except towards the end where I get the 
following error during linking ---

  LD      init/built-in.o
    LD      .tmp_vmlinux1
    arch/xtensa/kernel/built-in.o: In function `__down':
    arch/xtensa/kernel/built-in.o(.sched.text+0x11):dangerous 
relocation: l32r: literal placed after use: .sched.text.literal
    arch/xtensa/kernel/built-in.o(.sched.text+0x23):dangerous 
relocation: l32r: literal placed after use: .sched.text.literal
    arch/xtensa/kernel/built-in.o(.sched.text+0x5b):dangerous 
relocation: l32r: literal placed after use: .sched.text.literal
    arch/xtensa/kernel/built-in.o: In function `__down_interruptible':
    arch/xtensa/kernel/built-in.o(.sched.text+0x71):dangerous 
relocation: l32r: literal placed after use: .sched.text.literal
    arch/xtensa/kernel/built-in.o(.sched.text+0x89):dangerous 
relocation: l32r: literal placed after use: .sched.text.literal
    arch/xtensa/kernel/built-in.o(.sched.text+0xf3):dangerous 
relocation: l32r: literal placed after use: .sched.text.literal
    kernel/built-in.o: In function `schedule':
    kernel/built-in.o(.sched.text+0x1f):dangerous relocation: l32r: 
literal placed after use: .sched.text.literal
    kernel/built-in.o(.sched.text+0x31):dangerous relocation: l32r: 
literal placed after use: .sched.text.literal
....... many more such messages follow

Would be greatful if somebody could provide information in this regard

Regards
Satyaki Mukherjee

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s)and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender or administrator@tataelxsi.co.in

                 reply	other threads:[~2005-11-24 14:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4385CA66.8060709@tataelxsi.co.in \
    --to=satyaki@tataelxsi.co.in \
    --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

all inboxes | Powered by JetHome®