From: David Huggins-Daines <dhd@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Cc: debian-hppa@lists.debian.org
Subject: [parisc-linux] glibc 2.1.94 CVS merge, packages on the way, ABI breakage :(
Date: 03 Oct 2000 18:06:16 -0400 [thread overview]
Message-ID: <87aecl60mf.fsf@linuxcare.com> (raw)
Hi,
I've merged pehc CVS with glibc 2.1.94 release (no more tracking CVS
for me, too much pain).
The patch is clean enough that I'm able to just add it to the Debian
glibc 2.1.94 source package. So I will build that overnight
(hopefully) and upload it sometime soon.
For the time being there is a tarball at
ftp://puffin.external.hp.com/pub/parisc/binaries/userspace/glibc-2.1.94-20001003.tar.gz
But! Beware! It *will* break your system. Somehow, the versions of
a bunch of symbols in libm.so.6 reverted to GLIBC_2.0 from GLIBC_2.2
(don't ask me how this happened, math/Versions is still exactly the
same... I think our 2.1.92 had a bug in the script that generates the
version maps) and as a result, anything that links with libm will not
work. This includes fun things like perl, awk, some parts of
shellutils, etc. etc.
Sorry about this, but I guess we have no choice, our old libm.so was
broken.
I'm rebuilding perl, shellutils, and awk and expect to have new
packages on pehc real soon now. (perl's version will be 5.005.03-7.2,
shellutils and awk will be similarly bumped)
--
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
next reply other threads:[~2000-10-03 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-03 22:06 David Huggins-Daines [this message]
2000-10-03 22:23 ` [parisc-linux] glibc 2.1.94 CVS merge, packages on the way, ABI breakage :( Ulrich Drepper
2000-10-03 22:28 ` David Huggins-Daines
2000-10-03 22:42 ` Ulrich Drepper
2000-10-04 1:23 ` David Huggins-Daines
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=87aecl60mf.fsf@linuxcare.com \
--to=dhd@linuxcare.com \
--cc=debian-hppa@lists.debian.org \
--cc=parisc-linux@thepuffingroup.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.