From: Brian Murphy <brm@tt.dk>
To: David Kesselring <dkesselr@mmc.atmel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: odd link error
Date: Wed, 23 Jul 2003 16:26:42 +0200 [thread overview]
Message-ID: <3F1E9B22.8000604@tt.dk> (raw)
In-Reply-To: Pine.GSO.4.44.0307230844470.17973-100000@ares.mmc.atmel.com
David Kesselring wrote:
>I know my build for a custom board isn't right but it got through the
>compiles only to get this link error. Does anyone know what it might point
>to?
>
>mips64el-linux-ld --oformat elf32-tradlittlemips -G 0 -static -T
>arch/mips64/ld.script.elf32 -Ttext arch/mips64/kernel/head.o
>arch/mips64/kernel/init_task.o init/main.o init/version.o init/do_mounts.o
>\
> --start-group \
> arch/mips64/kernel/kernel.o arch/mips64/mm/mm.o kernel/kernel.o
>mm/mm.o fs/fs.o ipc/ipc.o arch/mips/math-emu/fpu_emulator.o
>arch/mips/ramdisk/ramdisk.o \
> drivers/char/char.o drivers/block/block.o drivers/misc/misc.o
>drivers/net/net.o drivers/media/media.o \
> net/network.o \
> arch/mips64/lib/lib.a
>/home/dkesselr/stbsw/linux/linux-64sead/lib/lib.a \
> --end-group \
> -o vmlinux
>mips64el-linux-ld: invalid hex number `arch/mips64/kernel/head.o'
>make: *** [vmlinux] Error 1
>
>
>
-Ttext expects an argument, the hex number mentioned, and it is for some
reason missing.
Since
arch/mips64/kernel/head.o
is not a valid hex number the build fails. You probably have some make
variable which is not
defined which should be. You should look at the makefile which contains
the linker line
and find -Ttext $(MISSING_VARIABLE) and find out why MISSING_VARIABLE is
not set.
/Brian
next prev parent reply other threads:[~2003-07-23 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 12:48 odd link error David Kesselring
2003-07-23 14:26 ` Brian Murphy [this message]
2003-07-23 16:52 ` Ralf Baechle
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=3F1E9B22.8000604@tt.dk \
--to=brm@tt.dk \
--cc=dkesselr@mmc.atmel.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