Difference between revisions of "Porting to x86-64 (AMD64, EM64T)"
m (removed historical page from its category list) |
|||
| (6 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{historical}} | ||
| + | |||
== Current status == | == Current status == | ||
| − | The x86-64 port is | + | The x86-64 port is essentially complete, modulo possible bugs. But between releases, during the development cycle, it is always likely that for a given milestone that OOo fails to build on x86_64, or that new 32bit-isms are introduced. Help is always appreciated to catch these problems early, or to recognize that there are other more subtle problems that we're unaware of. |
| − | The work | + | 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: | ||
| Line 31: | Line 33: | ||
* Find a bug (crash, missing functionality, ...) | * Find a bug (crash, missing functionality, ...) | ||
* Fix it ;-) It might be either in the ooo-build patches, or up-stream | * Fix it ;-) It might be either in the ooo-build patches, or up-stream | ||
| − | * [http://qa.openoffice.org/issue_handling/submission_gateway.html#code_module File] the problem & the solution to the | + | * [http://qa.openoffice.org/issue_handling/submission_gateway.html#code_module File] the problem & the solution to the [http://www.openoffice.org/issues/query.cgi 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 | ** 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 | * 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_Communication|IRC]]. | Should you have questions, please contact ''caolan'', ''kendy'', ''martink'', or ''paveljanik'' on [[IRC_Communication|IRC]]. | ||
| − | |||
| − | |||
Latest revision as of 07:49, 22 June 2012
This page is archived for historical reasons only. It is no longer maintained and information may not be current.
Current status
The x86-64 port is essentially complete, modulo possible bugs. But between releases, during the development cycle, it is always likely that for a given milestone that OOo fails to build on x86_64, or that new 32bit-isms are introduced. Help is always appreciated to catch these problems early, or to recognize that there are other more subtle problems that we're unaware of.
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.
