From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Michael Schmitz <schmitz@zirkon.biophys.uni-duesseldorf.de>,
Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Thomas Graichen <graichen@innominate.de>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: openoffice on ppc anyone?
Date: Thu, 19 Oct 2000 12:21:22 -0400 [thread overview]
Message-ID: <200010191621.LAA28113@lists.linuxppc.org> (raw)
Hi,
> Well I've run almost every glibc since gary thomas started releasing 'em
> way back when (thanks gary!) and I've been lucky so far. :)
Me too! The only real issue for *robust* native threads use are to stay with at least with glibc-2.1.3 (glibc-2.1.2 has some problems with the jdk).
When choosing a glibc-2.1.3 version, stick with either the glibc-2.1.3-5a-rpm which shipped with YDL and LinuxPPC I think) from Franz or his very latest glibc-2.1.3-15f rpm because the intermediate versions had native threads bugs introduced after the glibc-2.1.3 branch was completed (bug fixes which made new bugs!).
The jdk 1.2.2 FCS should be fine for the open office release since it is basically bug for bug compatible with the x86 jdk 1.2.2 (and Sun's jdk 1.2.2 for that matter).
If the jdk 1.2.2 runs into any trouble, let me know and I will fix it and make a special binary for anyone working on the openoffice port (or anyone for that matter).
Just let me know.
Kevin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-10-19 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-19 16:21 Kevin B. Hendricks [this message]
2000-10-19 17:47 ` openoffice on ppc anyone? Michael Schmitz
-- strict thread matches above, loose matches on Subject: below --
2000-10-17 5:23 Thomas Graichen
2000-10-17 19:06 ` Michael Schmitz
2000-10-18 11:17 ` Geert Uytterhoeven
2000-10-18 20:08 ` Michael Schmitz
2000-10-19 0:20 ` Tom Rini
2000-10-19 8:00 ` Michael Schmitz
2000-10-19 15:03 ` Tom Rini
2000-10-19 15:11 ` Michael Schmitz
2000-10-19 16:02 ` Tom Rini
2000-10-19 1:06 ` William Blew
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=200010191621.LAA28113@lists.linuxppc.org \
--to=khendricks@ivey.uwo.ca \
--cc=geert@linux-m68k.org \
--cc=graichen@innominate.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
--cc=schmitz@zirkon.biophys.uni-duesseldorf.de \
--cc=trini@kernel.crashing.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).