From: Keith Owens <kaos@melbourne.sgi.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: problems with insmod ...
Date: Sat, 21 Oct 2000 15:12:19 +1100 [thread overview]
Message-ID: <8345.972101539@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 20 Oct 2000 19:50:03 PDT." <39F1045B.21EF1851@mvista.com>
On Fri, 20 Oct 2000 19:50:03 -0700,
Jun Sun <jsun@mvista.com> wrote:
>I am using modutils v2.1.121, generated by binutils 2.8.1/egcs
>v1.0.3a/glibc 2.0.6.
>
>BTW, I seem to remember someone said the modutils 2.1.121 is not good
>MIPS. Which version is good?
2.1.121 is over two years old and is missing several mips patches.
There is no good reason to use 2.1.121, modutils 2.3 is backwards
compatible.
The last mips specific patch was in modutils 2.3.15. 2.3.18 ignores
empty relocate sections which I believe were a problem for several
architectures, possibly including mips. 2.3.19 will be released this
weekend and includes a mips patch to fix a minor problem which I doubt
anybody has ever hit. If you need modutils now, use 2.3.18, if you can
wait 48 hours, wait for 2.3.19.
ftp://ftp.<country>.kernel.org/pub/linux/kernel/utils/modutils/v2.3.
next prev parent reply other threads:[~2000-10-21 4:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-21 2:50 problems with insmod Jun Sun
2000-10-21 3:11 ` Ralf Baechle
2000-10-21 4:12 ` Keith Owens [this message]
2000-10-23 18:45 ` Jun Sun
2000-10-23 22:32 ` Keith Owens
2000-10-24 0:40 ` Ralf Baechle
2000-10-24 1:08 ` Jun Sun
2000-10-24 1:18 ` Ralf Baechle
2000-10-24 1:18 ` Ralf Baechle
2000-10-23 22:42 ` Brady Brown
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=8345.972101539@ocs3.ocs-net \
--to=kaos@melbourne.sgi.com \
--cc=jsun@mvista.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