Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-amd64
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-amd64@g.o
From: Hanno Meyer-Thurow <h.mth@...>
Subject: Re: openoffice 2 compiles?
Date: Tue, 8 Nov 2005 18:23:57 +0100
On Tue, 08 Nov 2005 17:31:14 +0100
Sebastian Redl <sebastian.redl@...> wrote:

> >If I say something wrong anyone please correct me! Thanks.

> Well, I disagree that the code needs a full rewrite. Why? All it needs 
> is correcting all places where it attempts to store pointers in 32-bit 
> variables. Admittedly, in the core of UNO this might happen a LOT (due 
> to its nature it does a lot of direct memory manipulation), but there's 
> no real reason why it should be re-written from scratch.
> If the UNO runtime violated other portability issues (such as code 
> execution protection), it wouldn't run at all in 64-bit mode, perhaps 
> not even when compiled as 32-bit.

I am no programmer and what you say sure is correct but of what i listened
from some OOo devs is that some parts (big or small) need rewrite to
get stable on amd64. However...

Latest information I read:
http://artax.karlin.mff.cuni.cz/~kendy/ooo/OOoCon-2005/
-- 
gentoo-amd64@g.o mailing list


Replies:
Re: openoffice 2 compiles?
-- Barry . SCHWARTZ
References:
openoffice 2 compiles?
-- Chris Smart
Re: openoffice 2 compiles?
-- Hanno Meyer-Thurow
Re: openoffice 2 compiles?
-- Sebastian Redl
Navigation:
Lists: gentoo-amd64: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: openoffice 2 compiles?
Next by thread:
Re: openoffice 2 compiles?
Previous by date:
Re: openoffice 2 compiles?
Next by date:
Re: openoffice 2 compiles?


Updated Jun 17, 2009

Summary: Archive of the gentoo-amd64 mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.