From: Randolph Chung <randolph@tausq.org>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] glibc update
Date: Wed, 17 Oct 2001 12:23:13 -0700 [thread overview]
Message-ID: <20011017122313.C4123@tausq.org> (raw)
glibc 2.2.4-3 has been uploaded to Debian's incoming direction and
should be installed in today's archive run.
it was lightly tested by lamont and myself before upload... please do
report any problems you find.
note that after i sent out my email yesterday about glibc, we ran into
some other obstacles...
1. the glibc i uploaded is actually built with a fairly old binutils
(version 2.11.90.0.7-2.0.1). There could well be many binutils bug fixes
since then, but at least for this case it lets us build glibc without
the segfaults we see with the newer binutils
2. the newest binutils (2.11.92.0.5-3), also in incoming, doesn't appear
to address the glibc build issue as i originally thought. we still get
ld.so segfaults as Carlos has observed earlier. Perhaps someone (Carlos,
Alan, Rob?) can look at the binutils changes since then can see what
broke?
3. with the glibc build (using old binutils) some of the linuxthreads
tests are failing. in particular there's one case where it seems to get
into a deadlock. i left it running overnight and it's still stuck ...
i don't know if this has always been broken though.
Build logs for #3 and #2 above can be found at:
#3: http://people.debian.org/~tausq/glibc.build.log2
#2: http://people.debian.org/~tausq/glibc.build.log5
randolph
--
@..@ http://www.TauSq.org/
(----)
( >__< )
^^ ~~ ^^
next reply other threads:[~2001-10-17 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 19:23 Randolph Chung [this message]
2001-10-18 10:44 ` [parisc-linux] glibc update Richard Allen
2001-10-18 14:10 ` Matthew Wilcox
2001-10-18 15:49 ` Kaj-Michael Lang
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=20011017122313.C4123@tausq.org \
--to=randolph@tausq.org \
--cc=parisc-linux@parisc-linux.org \
/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