Skip to contentSkip to conversation

PROBLEM: Compiling Linux kernel 2.6.13.2 for Xtensa

DISCUSSION Satyaki Mukherjee 1 participant 1 message Nov 24, 2005

lore
Share & tools
lore
#0 lore 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 [email protected]