public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel•crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k•org>
Cc: Michael Schmitz <schmitz@opal•biophys.uni-duesseldorf.de>,
	Thomas Graichen <graichen@innominate•de>,
	linuxppc-dev@lists•linuxppc.org
Subject: Re: openoffice on ppc anyone?
Date: Wed, 18 Oct 2000 17:20:44 -0700	[thread overview]
Message-ID: <20001018172044.E15104@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.4.10.10010181316430.841-100000@cassiopeia.home>; from geert@linux-m68k.org on Wed, Oct 18, 2000 at 01:17:17PM +0200


On Wed, Oct 18, 2000 at 01:17:17PM +0200, Geert Uytterhoeven wrote:
>
> On Tue, 17 Oct 2000, Michael Schmitz wrote:
> > > is anyone trying to get the now opensource staroffice to compile on
> > > linux/ppc?
> >
> > I've given up on this - the build tools included in the source package are
> > binary only (Intel or Sparc), no sources so far as I can see, and the
> > stuff in config_office has a number of hardcoded assumptions that make
> > life miserable (gcc version == 2.95.2, jdk 1.2.2 which requires glibc
> > 2.1.3, Linux only exists on Intel and Sparc, ...). Basically, it sucks.
>                               ^^^^^^^^^^^^^^^
> Look at the bright side: at least the code should be endianness and 64-bit
> clean :-)

Well, maybe anyways.  Are you sure it's Linux/x86 and Linux/sparc not
Linux/x86 and Solaris/sparc and Solaris/x86? :)  Anyways,
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?)

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-10-19  0:20 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 [this message]
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
  -- 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=20001018172044.E15104@opus.bloom.county \
    --to=trini@kernel$(echo .)crashing.org \
    --cc=geert@linux-m68k$(echo .)org \
    --cc=graichen@innominate$(echo .)de \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    --cc=schmitz@opal$(echo .)biophys.uni-duesseldorf.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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