From: Ralf Baechle <ralf@linux-mips.org>
To: Guo Michael <michael_e_guo@hotmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Which compiler should I use to make mips64 kernel
Date: Tue, 6 May 2003 14:40:29 +0200 [thread overview]
Message-ID: <20030506124029.GA2180@linux-mips.org> (raw)
In-Reply-To: <BAY8-F125H3IhA1qfT700013d0f@hotmail.com>
On Tue, May 06, 2003 at 02:54:52PM +0800, Guo Michael wrote:
> mips64el-linux-ld -r -o kernel.o sched.o dma.o fork.o exec_domain.o
> panic.o printk.o module.o exit.o itimer.o info.o time.o softirq.o
> resource.o sysctl.o acct.o capability.o ptrace.o timer.o user.o signal.o
> sys.o kmod.o context.o ksyms.o
> mips64el-linux-ld: BFD 2.13.2.1 assertion fail elflink.h:5117
This is a known but not yet fixed problem that only seems to hit certain
kernel configurations; I believe it somehow tied to little endianess also.
Ralf
next prev parent reply other threads:[~2003-05-06 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 6:54 Which compiler should I use to make mips64 kernel Guo Michael
2003-05-06 12:40 ` Ralf Baechle [this message]
2003-05-08 19:21 ` Maciej W. Rozycki
2003-05-06 13:04 ` Maciej W. Rozycki
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=20030506124029.GA2180@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=michael_e_guo@hotmail.com \
/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