Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Keith Owens <kaos@melbourne.sgi.com>
To: Ian Soanes <ians@lineo.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Insmod messages and modules space
Date: Tue, 24 Apr 2001 08:57:55 +1000	[thread overview]
Message-ID: <12715.988066675@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Tue, 10 Apr 2001 09:55:16 BST." <3AD2CA74.DCC850EF@lineo.com>

On Tue, 10 Apr 2001 09:55:16 +0100, 
Ian Soanes <ians@lineo.com> wrote:
>> On Mon, Apr 09, 2001 at 08:10:16PM +0200, Shay Deloya wrote:
>> > 2. I keep getting in insmod of busybox pkg , "relocation overflow" message
>> > especially on printk symbols
>
>Compiling with -mlong-calls worked for me when I had the same problem
>(modutils 2.4.5).

Compiling what with -mlong-calls, modutils or the kernel modules?  I
guess it must be the modules, in which case adding
  MODFLAGS += -mlong-calls
in arch/$(ARCH)/Makefile is the best fix.

  reply	other threads:[~2001-04-23 22:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-09 18:10 Insmod messages and modules space Shay Deloya
2001-04-09 19:14 ` Ralf Baechle
2001-04-10  8:55   ` Ian Soanes
2001-04-23 22:57     ` Keith Owens [this message]
2001-04-24  8:22       ` Ian Soanes

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=12715.988066675@ocs3.ocs-net \
    --to=kaos@melbourne.sgi.com \
    --cc=ians@lineo.com \
    --cc=linux-mips@oss.sgi.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