From: Ralf Baechle <ralf@oss.sgi.com>
To: Jeff Harrell <jharrell@ti.com>
Cc: linux-mips@oss.sgi.com, bbrown@ti.com
Subject: Re: Question concerning necessary libraries for 2.4.x kernel upgrade
Date: Fri, 7 Jul 2000 02:46:08 +0200 [thread overview]
Message-ID: <20000707024608.D2303@bacchus.dhis.org> (raw)
In-Reply-To: <3964C025.623F7F5@ti.com>; from jharrell@ti.com on Thu, Jul 06, 2000 at 11:21:41AM -0600
On Thu, Jul 06, 2000 at 11:21:41AM -0600, Jeff Harrell wrote:
> I am currently upgrading my MIPS development board (Atlas) that contains
> a R4Kc (jade core)
> and version 2.2.12 of the Linux kernel to a 2.4.x series kernel. I
> believe the libraries and applications
> were built off of the hardhat distribution. We are able to run the
> 2.4.x version of the kernel on the Atlas
> board but are seeing problems with some of the executables. I examined
> the Changes file and am in the
> process of upgrading the following binaries/libraries..
>
> GNU C 2.7.2.3
2.7.2.3 may work or not. Most people are using egcs 1.0.3a, so I recommend
using that one.
> binutils 2.9.1.0.22
DON'T touch, stick with 2.8.1.
> util-linux 2.10g
> modutils 2.3.0
I have no reports about modutils 2.3.0.
> e2fsprogs 1.18
> pcmcia-cs 3.1.13
> ppp 2.4.0b1
>
> I am seeing problems with executables such as awk, groff, troff, etc.
> Will I need to rebuild each of these
> applications against the new libraries to run or should they still
> function after I have upgraded the previously
> mentioned packages? Are there mipsel version of these packages (either
> source or binaries) available somewhere?
You can try the DECstation package (see howto) or get the src.rpm
packages from oss.sgi.com which has a preliminary RH 6.0 port. The packages
should build for little endian also.
Ralf
next prev parent reply other threads:[~2000-07-07 0:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-06 17:21 Question concerning necessary libraries for 2.4.x kernel upgrade Jeff Harrell
2000-07-07 0:46 ` Ralf Baechle [this message]
2000-07-07 15:03 ` Wichert Akkerman
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=20000707024608.D2303@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=bbrown@ti.com \
--cc=jharrell@ti.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