From: Ralf Baechle <ralf@linux-mips.org>
To: David Kesselring <dkesselr@mmc.atmel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: odd link error
Date: Wed, 23 Jul 2003 18:52:32 +0200 [thread overview]
Message-ID: <20030723165231.GA5851@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.4.44.0307230844470.17973-100000@ares.mmc.atmel.com>
On Wed, Jul 23, 2003 at 08:48:03AM -0400, 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?
Seems the SEAD bits in your Makefile are incomplete, arch/mips64/Makefile
should contain this:
[...]
#
# MIPS SEAD board
#
ifdef CONFIG_MIPS_SEAD
LIBS += arch/mips/mips-boards/sead/sead.o \
arch/mips/mips-boards/generic/mipsboards.o
SUBDIRS += arch/mips/mips-boards/generic arch/mips/mips-boards/sead
LOADADDR := 0x80100000
endif
[...]
Ralf
prev parent reply other threads:[~2003-07-23 16:52 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
2003-07-23 16:52 ` Ralf Baechle [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=20030723165231.GA5851@linux-mips.org \
--to=ralf@linux-mips.org \
--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