From: Ralf Baechle <ralf@oss.sgi.com>
To: Michael Shmulevich <michaels@jungo.com>
Cc: Shay Deloya <shay@jungo.com>, linux-mips@oss.sgi.com
Subject: Re: insmod problems
Date: Thu, 10 May 2001 15:46:39 -0300 [thread overview]
Message-ID: <20010510154639.B1269@bacchus.dhis.org> (raw)
In-Reply-To: <3AFA56F8.9090504@jungo.com>; from michaels@jungo.com on Thu, May 10, 2001 at 11:53:12AM +0300
On Thu, May 10, 2001 at 11:53:12AM +0300, Michael Shmulevich wrote:
> 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.
Without further explanation this one just sounds bizarre for now.
There always have been differences between the code generated by binutils
in the various versions; the resulting changes may result in different
behaviour of a broken programs. These are fun to debug to say the least.
The other possibility would be binutils bugs but I'm not aware of one
with the effect you described.
Ralf
next prev parent reply other threads:[~2001-05-10 22:29 UTC|newest]
Thread overview: 15+ 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
2001-05-10 18:46 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-04 16:33 Insmod problems Nav Mundi
2001-12-04 16:42 Tyler BIRD
[not found] <sc0c9a91.036@mail-smtp.uvsc.edu>
2001-12-04 17:06 ` Michael Zhu
2001-12-04 16:55 ` Thiago Rondon
2001-12-04 17:47 ` rddunlap
2001-12-04 17:30 Tyler BIRD
[not found] <81C25B579A82D31192BE00105A812084028931E9@AUGUSTA>
2001-12-04 18:13 ` Michael Zhu
[not found] <sc0ca5e8.017@mail-smtp.uvsc.edu>
2001-12-04 18:20 ` Michael Zhu
2001-12-04 18:33 ` Tommy Reynolds
2001-12-04 19:10 ` Alan Cox
2001-12-04 18:24 Tyler BIRD
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=20010510154639.B1269@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=michaels@jungo.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 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.