Difference between revisions of "Porting to x86-64 (AMD64, EM64T)"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Current status)
(Current status)
Line 3: Line 3:
 
The x86-64 port is still work in progress, but it is already usable in the current state.  The help is appreciated, join the project! :-)
 
The x86-64 port is still work in progress, but it is already usable in the current state.  The help is appreciated, join the project! :-)
  
The work is based on ''ooo64bit02'' [[CWS|Child Workspace (CWS)]].  Most of the patches were already integrated to SRC680 in various other CWS's, because ooo64bit02 was too huge to be integrated as a whole.
+
The work was originally based on ''ooo64bit02'' [[CWS|Child Workspace (CWS)]].  It was too huge to be integrated as a whole, so it was split to various smaller CWS'es, and integrated to SRC680 (HEAD); then more fixes were introduced.
  
 
More info:
 
More info:

Revision as of 17:26, 11 May 2007

Current status

The x86-64 port is still work in progress, but it is already usable in the current state. The help is appreciated, join the project! :-)

The work was originally based on ooo64bit02 Child Workspace (CWS). It was too huge to be integrated as a whole, so it was split to various smaller CWS'es, and integrated to SRC680 (HEAD); then more fixes were introduced.

More info:

How to get it

Get the latest SRC680 development sources, and follow the general Getting It, Building, Installing, Running sections. Don't forget to use --with-system-libs while configuring.

It is recommended to use a recent distro for building, like SUSE 10.1 or newer. gcc should be at least 3.4.1 with enum+visibility patches, 4.x is probably the best choice.

It is very probable that you'll have problems with Java - some of the VM's have problems to build OOo on x86-64.

Java

You have to have a 64bit Java installed. The following are known to work:

  • gcj 4.0.1 - e.g. in SUSE 10.1 installation, works out of the box
  • Blackdown Java - reported to work

How to help

Generally

  • Compile it
  • Find a bug (crash, missing functionality, ...)
  • Fix it ;-) It might be either in the ooo-build patches, or up-stream
  • File the problem & the solution to the IssueZilla if it is up-stream, or send it to openoffice@lists.ximian.com if it is in the ooo-build patches
    • Ensure that you CC 'kendy', 'pjanik', and 'cmc' on the report to get a quick response
  • If the underlying problem is a new problem archetype - try to find & fix all other instances of it

Should you have questions, please contact caolan, kendy, martink, or paveljanik on IRC.

Personal tools