From: Hanno Meyer-Thurow <h.mth@web.de>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] openoffice 2 compiles?
Date: Tue, 8 Nov 2005 18:23:57 +0100 [thread overview]
Message-ID: <20051108182357.c2950616.h.mth@web.de> (raw)
In-Reply-To: <4370D2D2.8000507@getdesigned.at>
On Tue, 08 Nov 2005 17:31:14 +0100
Sebastian Redl <sebastian.redl@getdesigned.at> 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@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-08 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 6:20 [gentoo-amd64] openoffice 2 compiles? Chris Smart
2005-11-08 12:56 ` Hanno Meyer-Thurow
2005-11-08 16:31 ` Sebastian Redl
2005-11-08 17:23 ` Hanno Meyer-Thurow [this message]
2005-11-08 17:30 ` Barry.SCHWARTZ
2005-11-08 18:15 ` Sebastian Redl
2005-11-08 22:17 ` Chris Smart
-- strict thread matches above, loose matches on Subject: below --
2005-11-08 6:36 Dmitri Pogosyan
2005-11-08 7:16 ` Chris Smart
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=20051108182357.c2950616.h.mth@web.de \
--to=h.mth@web.de \
--cc=gentoo-amd64@lists.gentoo.org \
/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