From: Thomas Graichen <hidden> Date: 2000-10-17 05:23:37
i hope it's ok to ask this on the dev list - but i assume that it's
not a trivial task - so i hope it's the right list and thus ok ...
is anyone trying to get the now opensource staroffice to compile on
linux/ppc?
http://www.openoffice.org
t
--
thomas.graichen@innominate.de
technical director innominate AG
clustering & security networking people
tel: +49.30.308806-13 fax: -77 http://innominate.de
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
From: Michael Schmitz <hidden> Date: 2000-10-17 19:06:28
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.
Michael
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
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/
From: Michael Schmitz <hidden> Date: 2000-10-18 20:08:53
quoted
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 :-)
Byte endianness clean, perhaps. 64 bit clean? You wish: sparc64 was not an
explicit option. What does uname -m on a sparc64 give?
Michael
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
From: William Blew <hidden> Date: 2000-10-19 01:06:57
On Wed, 18 Oct 2000, Geert Uytterhoeven wrote:
On Tue, 17 Oct 2000, Michael Schmitz wrote:
quoted
quoted
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 :-)
I strongly suggest that anyone even thinking about this take a look at the
site. It has detailed build instructions that include how to build the
build tools.
--
William Blew, wblew@home.com
Gamer by Choice, Geek by Birth
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/