From: Kevin Hendricks <khendricks@ivey.uwo.ca>
To: linuxppc-dev@lists.linuxppc.org
Subject: Fwd: Re: More with Mozilla and glibc
Date: Sat, 11 Sep 1999 13:28:52 -0400 [thread overview]
Message-ID: <99091113302601.02027@localhost.localdomain> (raw)
---------- Forwarded Message ----------
Subject: Re: More with Mozilla and glibc
Date: Sat, 11 Sep 1999 08:49:01 -0400
From: Kevin Hendricks <khendricks@ivey.uwo.ca>
On Sat, 11 Sep 1999, you wrote:
> Wow. Well, I'm still thinking that my Mozilla problem is glibc related, even if
> the gdb output is bogus ; ).
You may be right. The native threads jdk works with glibc 2.1.1 and won't work
with glibc 2.1.2 since they made some new semaphore functions. I do not
recommend using glibc 2.1.2 yet for native threads stuff until they get the new
semaphore functions fixed.
'
Kevin
Has anyone else run into problems with the glibc 2.1.2 new semaphore functions?
Has glibc 2.1.2 been officially released yet and if so where can I download the
offical glibc 2.1.2 source to look at these new semaphore functions.
Thanks,
Kevin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~1999-09-11 17:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=99091113302601.02027@localhost.localdomain \
--to=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).