From: Tom Rini <trini@kernel.crashing.org>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: 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 08:03:31 -0700 [thread overview]
Message-ID: <20001019080331.H15104@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.4.10.10010190955320.28045-100000@opal.biophys.uni-duesseldorf.de>; from schmitz@opal.biophys.uni-duesseldorf.de on Thu, Oct 19, 2000 at 10:00:20AM +0200
On Thu, Oct 19, 2000 at 10:00:20AM +0200, Michael Schmitz wrote:
> > http://porting.openoffice.org/ implies anwyays the src for the tools should be
> > around. Finally, gcc 2.95.2 (or 2.95.3) and glibc 2.1.3 are good for you.
> > JDK 1.2.2 should be fine (Kevin?)
>
> The day I tried (Oct. 13) nothing besides the raw source tarball was up on
> the site. I'll check again though. I've read to different and conflicting
> build instructions (one suggested JDK 1.1.8, the other 1.2.2).
Well, make sure to update your tree. One of the mailing lists on that page
says some diffs for linux/ppc have been checked in.
> I'm already using a recent gcc 2.95.3 but libc upgrades always freak me
> out ...
It's not as bad as it used to be. :)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-19 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-17 5:23 openoffice on ppc anyone? 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 [this message]
2000-10-19 15:11 ` Michael Schmitz
2000-10-19 16:02 ` Tom Rini
2000-10-19 1:06 ` William Blew
-- strict thread matches above, loose matches on Subject: below --
2000-10-19 16:21 Kevin B. Hendricks
2000-10-19 17:47 ` Michael Schmitz
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=20001019080331.H15104@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=graichen@innominate.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
/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.