From: Daniel Jacobowitz <dan@debian.org>
To: David Kesselring <dkesselr@mmc.atmel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Relocation errors
Date: Mon, 27 Oct 2003 10:14:21 -0500 [thread overview]
Message-ID: <20031027151421.GA27279@nevyn.them.org> (raw)
In-Reply-To: <Pine.GSO.4.44.0310271002480.19642-100000@ares.mmc.atmel.com>
Take a look at /usr/include/elf.h:
#define R_MIPS_LITERAL 8 /* 16 bit literal entry */
In this case it's not very informative. But the problem is probably
mismatched CFLAGS. Take another look at the options the kernel is
built with - you lost -G 0. See if that does it.
On Mon, Oct 27, 2003 at 10:06:53AM -0500, David Kesselring wrote:
> It is type 8. Any ideas? This is from an intel driver that I've cross
> compiled for mips. I used these options;
> -mcpu=r4600 -mips2 -mno-abicalls -fno-pic -mlong-calls -Wa,--trap -DMODULE
> -pipe -O3 -fomit-frame-pointer -fno-strict-aliasing
>
> Thanks, David
>
> On Mon, 27 Oct 2003, Daniel Jacobowitz wrote:
>
> > On Mon, Oct 27, 2003 at 08:55:19AM -0500, David Kesselring wrote:
> > > I'm getting the error "Unhandled relocation of type xx" on insmod. Are the
> > > "types" documented somewhere? I am I correct that these "types" are
> > > architecture specific?
> >
> > Yes. Try an ELF specification - there's a MIPS processor supplement
> > (psABI) floating around. What's the "xx"?
> >
> > --
> > Daniel Jacobowitz
> > MontaVista Software Debian GNU/Linux Developer
> >
> >
>
> David Kesselring
> Atmel MMC
> dkesselr@mmc.atmel.com
> 919-462-6587
>
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-10-27 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 13:55 Relocation errors David Kesselring
2003-10-27 14:58 ` Daniel Jacobowitz
2003-10-27 15:06 ` David Kesselring
2003-10-27 15:14 ` Daniel Jacobowitz [this message]
2003-10-27 16:06 ` 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=20031027151421.GA27279@nevyn.them.org \
--to=dan@debian.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