From: Thomas Koeller <thomas.koeller@baslerweb.com>
To: linux-mips@linux-mips.org
Subject: linker script problem
Date: Fri, 26 Mar 2004 13:49:41 +0100 [thread overview]
Message-ID: <200403261349.41783.thomas.koeller@baslerweb.com> (raw)
Hi,
I just ran into the folowing problem when building a kernel.
This is the first time I build a MIPS kernel, and so I may
be making mistakes. Here's what I found:
When building the kernel, the linker chokes on
arch/mips/kernel/vmlinux.lds.s, because it contains
OUTPUT_ARCH(mips)
ENTRY(kernel_entry)
jiffies = jiffies_64 + 4;
SECTIONS
{
. = ;
*** ^ ***
This has been generated from arch/mips/kernel/vmlinux.lds.S,
which contains
. = LOADADDR;
which is in turn generated from arch/mips/kernel/.vmlinux.lds.s.cmd,
which contains
cmd_arch/mips/kernel/vmlinux.lds.s := mips-linux-gcc -E -Wp,-MD,arch/mips/kernel/.vmlinux.lds.s.d -nostdinc -iwithprefix include -D__KERNEL__ -Iinclude -D__KERNEL__ -Iinclude -D__ASSEMBLY__ -I /home/GERMANY/tkoeller/mips-linux/build/linux/include/asm/gcc -G 0 -mno-abicalls -fno-pic -pipe -finline-limit=100000 -mabi=32 -march=r5000 -Wa,-32 -Wa,-march=r5000 -Wa,-mips4 -Wa,--trap -Iinclude/asm-mips/mach-generic -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -I /home/GERMANY/tkoeller/mips-linux/build/linux/include/asm/gcc -G 0 -mno-abicalls -fno-pic -pipe -finline-limit=100000 -mabi=32 -march=r5000 -Wa,-32 -Wa,-march=r5000 -Wa,-mips4 -Wa,--trap -Iinclude/asm-mips/mach-generic -O2 -fomit-frame-pointer -D"LOADADDR=" -D"JIFFIES=jiffies_64 + 4" -imacros /home/GERMANY/tkoeller/mips-linux/build/linux/include/asm-mips/sn/mapped_kernel.h -P -C -Umips -o arch/mips/kernel/vmlinux.lds.s arch/mips/kernel/vmlinux.lds.S
in line #1. The -D"LOADADDR=" looks suspicious, but I
have not been able to trace the problem beyond this point.
Can anybody help out?
tk
--
--------------------------------------------------
Thomas Koeller, Software Development
Basler Vision Technologies
thomas dot koeller at baslerweb dot com
http://www.baslerweb.com
==============================
next reply other threads:[~2004-03-26 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 12:49 Thomas Koeller [this message]
2004-03-26 12:57 ` linker script problem Thiemo Seufer
2004-03-26 13:55 ` Thomas Koeller
2004-03-26 14:13 ` Maciej W. Rozycki
2004-03-26 14:21 ` Thiemo Seufer
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=200403261349.41783.thomas.koeller@baslerweb.com \
--to=thomas.koeller@baslerweb.com \
--cc=linux-mips@linux-mips.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