From: "Gilad Benjamini" <gilad@riverhead.com>
To: <linux-mips@linux-mips.org>
Subject: insmod failure: "Unhandled relocation" errors
Date: Tue, 14 Jan 2003 12:06:46 +0200 [thread overview]
Message-ID: <001801c2bbb4$a6177de0$7100000a@riverhead.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
Hi,
I've built,compiled and ran successfully a 64 bit kernel on my
mips64 platform. Kernel was compiled with support for 32 bit binaries.
I am now trying to insert a module, a standard module from
the kernel tree, and get lots of errors such as:
"Unhandled relocation of type 18 for"
or
"Unhandled relocation of type 18 for <function_name>"
How can this be resolved ?
TIA
[-- Attachment #2: Type: text/html, Size: 1958 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Gilad Benjamini" <gilad@riverhead.com>
To: linux-mips@linux-mips.org
Subject: insmod failure: "Unhandled relocation" errors
Date: Tue, 14 Jan 2003 12:06:46 +0200 [thread overview]
Message-ID: <001801c2bbb4$a6177de0$7100000a@riverhead.com> (raw)
Message-ID: <20030114100646.IOMfaoYoQIKlomfuy_csTuRK2MXsIQ6EqTrq_AujCps@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
Hi,
I've built,compiled and ran successfully a 64 bit kernel on my
mips64 platform. Kernel was compiled with support for 32 bit binaries.
I am now trying to insert a module, a standard module from
the kernel tree, and get lots of errors such as:
"Unhandled relocation of type 18 for"
or
"Unhandled relocation of type 18 for <function_name>"
How can this be resolved ?
TIA
[-- Attachment #2: Type: text/html, Size: 1958 bytes --]
next reply other threads:[~2003-01-14 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 10:06 Gilad Benjamini [this message]
2003-01-14 10:06 ` insmod failure: "Unhandled relocation" errors Gilad Benjamini
2003-01-14 17:05 ` Ralf Baechle
2003-01-14 19:14 ` Greg Lindahl
2003-01-15 12:15 ` Ralf Baechle
2003-01-14 23:34 ` Keith Owens
2003-01-15 12:24 ` 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='001801c2bbb4$a6177de0$7100000a@riverhead.com' \
--to=gilad@riverhead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.