Post a Comment
> 32bit binaries will run fine on x86-64.
only if you have the necessary 32-bit libraries installed... OO.o is bloated enough already...
> But OO.o is still not compiled as 64bit code and won't be for a long time.
that's what i thought... i guess i'll just stick with koffice for now...
----If they've made the database app a little more stable this time around?
Seems that way. There is also support for using e-mail in mail merge now and Oo recognizes thunderbird address books if you want it too.
Some improvements to bulleting also and the whole app just feels a bit snappier/more stable.
I do recommend completely unistalling (even the app data) you old copy before installing the new one.
I am curious, anyone know if THIS was included?
http://www.nat.org/2005/november/#OpenOffice-startup-time
That "hack" requires modifications to glibc, binutils and the recompilation of many parts of the system; there is a bug-report in Gentoo bugzilla, open by Michael Meeks to gain some attention to his proposed patches: http://bugs.gentoo.org/show_bug.cgi?id=114008
The initial OO.o 2.0 release had numerous small (and yet annoying) glitches. I think it'll take several of these bugfix point releases before OO.o 2.0 becomes as smooth and reliable as OO.o 1.1 was (OO.o 1.0 was also quite buggy when it first came out). But it's good to see that they're working on it. :-)
For my Windows machine, I just installed to the previous install's install directory. In Linux, everything is an RPM, so you just -Uvh and you're good to go. Any changes you made to the soffice script will have to be redone though, but all your user settings will stay intact.
Why would you want to compile an office suite as a 64bit app?
If your spreadsheet or "base" requires more memory than that can be addressed with 32 bits (that is 4GB), then you should be looking for a different solution (e.g. an SQL server).
The same goes for serious 64bit+ number crunching, where performance may matter (yes, a 32bit app can do 64bit+ math).
Thus, unless an app needs to address more than 4GB of memory at _once_ or does lots of 64bit+ math, it should be compiled as a 32bit (not 64bit) excutable, as it will potentially run faster due to being able to pack more into each word - not wasting the remaining 32bits.



