From: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>
To: randolph@tausq.org, parisc-linux@parisc-linux.org
Subject: [randolph@tausq.org: [parisc-linux] glibc update]
Date: Wed, 17 Oct 2001 23:40:38 -0400 [thread overview]
Message-ID: <20011017234038.C1060@megatonmonkey.net> (raw)
R,
>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
I'll see about giving it a try on my 712/60 and 715/50's
>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?
Eventually I'll get that assembly trace done.
>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.
This reminds me, in general I keep forgetting to add the location of
/xxx/glibc-2.2.4/hppa-linux/obj to LD_LIBRARY_PATH. This nips some of
the tests in the bud since ld goes looking for the wrong library.
>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
Have you tried running the tests by hand and seeing what the output is?
What is the output of running:
/home/randolph/gcc-3.0/glibc-2.2.4/hppa-linux/obj/math/test-fenv.out
c.
next reply other threads:[~2001-10-18 3:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 3:40 Carlos O'Donell Jr. [this message]
2001-10-18 22:02 ` [randolph@tausq.org: [parisc-linux] glibc update] Randolph Chung
2001-10-19 5:17 ` Carlos O'Donell Jr.
2001-10-19 13:39 ` Matthew Wilcox
2001-10-19 16:06 ` John David Anglin
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=20011017234038.C1060@megatonmonkey.net \
--to=carlos@megatonmonkey.net \
--cc=parisc-linux@parisc-linux.org \
--cc=randolph@tausq.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 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.