Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Michael Shmulevich <michaels@jungo.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Shay Deloya <shay@jungo.com>, linux-mips@oss.sgi.com
Subject: Re: insmod problems
Date: Thu, 10 May 2001 11:53:12 +0300	[thread overview]
Message-ID: <3AFA56F8.9090504@jungo.com> (raw)
In-Reply-To: 20010508234036.A1216@bacchus.dhis.org



Ralf Baechle wrote:

> On Sun, May 06, 2001 at 07:13:43PM +0300, Shay Deloya wrote:
> 
> 
>> I have an old problem came up again and the old solution aren't helping.
>> Relocation overflow of type 4 for
>> Is it insmod knowen bugs that the relocation is done in bad way or 
>> a linker/compiler bug. I'm using compiler: egcs ver 1.0.3a
>> I'm checking this problem at the moment and looking for insmod bug.
> 
> 
> You'll have to upgrade to very current binutils which for mips*-linux
> targets default to elf32-trad{big,little}mips, not IRIX ELF format.  Also
> it seems your modutils are a bit rotten, get the latest from ftp.kernel.org.
> 
>   Ralf

On the same topic: same source (!!) 'insmod' executable compiled with 
new (2.10) binutils doesn't exibit such relocation problem.

What may be causing 'insmod' to be dependant on binutils which compile 
it? The module *.o is exactly same as it was before.


Sincerely yours,
Michael Shmulevich
______________________________________
Software Developer
Jungo - R&D
email: michaels@jungo.com
web: http://www.jungo.com
Phone: 1-877-514-0537(USA)  +972-9-8859365(Worldwide) ext. 233
Fax:   1-877-514-0538(USA)  +972-9-8859366(Worldwide)

  reply	other threads:[~2001-05-10  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-06 16:13 insmod problems Shay Deloya
2001-05-09  2:40 ` Ralf Baechle
2001-05-10  8:53   ` Michael Shmulevich [this message]
2001-05-10 18:46     ` 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=3AFA56F8.9090504@jungo.com \
    --to=michaels@jungo.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.com \
    --cc=shay@jungo.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