Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: linux-mips@oss.sgi.com, linux-mips@fnet.fr, linux-origin@oss.sgi.com
Subject: libc upgrade
Date: Fri, 22 Sep 2000 15:26:04 +0200	[thread overview]
Message-ID: <20000922152604.A2627@bacchus.dhis.org> (raw)

I've uploaded the hopefully last glibc 2.0.6 release to oss.sgi.com.  The
rpm package filenames are:

  glibc-2.0.6-6lm.src.rpm,
  glibc-2.0.6-6lm.mips.rpm,
  glibc-devel-2.0.6-6lm.mips.rpm,
  glibc-profile-2.0.6-6lm.mips.rpm,
  glibc-debug-2.0.6-6lm.mips.rpm

This release fix a number of bug that have been hanging in the dynamic
linker basically forever and is urgently recommended to install.

Once more rpm in it's stupidity being a static linked program breaks.  I
therefore also provide new rpm binaries:

  rpm-3.0-6.0lm.mips.rpm
  rpm-devel-3.0-6.0lm.mips.rpm

No new source package for rpm since this is just a recompile of the
package.  Not that also other software which has been statically linked
against libdl needs to be rebuilt against this library release.

IMPORTANT: you must install these new rpm binaries before you upgrade
glibc!

  Ralf

             reply	other threads:[~2000-09-22 13:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-22 13:26 Ralf Baechle [this message]
2000-09-25  9:24 ` libc upgrade Florian Lohoff
2000-09-25 11:20   ` Ralf Baechle
2000-09-25 14:15     ` Florian Lohoff
2000-09-25 20:14       ` Ralf Baechle
2000-09-25 23:04         ` Florian Lohoff
2000-09-26  0:46           ` Ralf Baechle
2000-09-26  8:37           ` Gleb O. Raiko
2000-09-26 10:36             ` Florian Lohoff
2000-09-26 21:06               ` Ralf Baechle
2000-09-26 17:48             ` Keith M Wesolowski
2000-09-26  8:30         ` Gleb O. Raiko
2000-09-26 22:47           ` 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=20000922152604.A2627@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.com \
    --cc=linux-origin@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