From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Thomas Graichen <graichen@innominate.de>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: openoffice on ppc anyone?
Date: Wed, 18 Oct 2000 13:17:17 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.10.10010181316430.841-100000@cassiopeia.home> (raw)
In-Reply-To: <Pine.LNX.4.10.10010172057330.27337-100000@opal.biophys.uni-duesseldorf.de>
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 :-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-18 11:17 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 [this message]
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
-- 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=Pine.LNX.4.10.10010181316430.841-100000@cassiopeia.home \
--to=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 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).