OpenBSD Journal

Call For Donations - New OpenOffice.org port build box needed

Contributed by mitja on from the we-ran-out-of-office-jokes dept.

In the shadow of recent good news about the state of OpenOffice.org suite on OpenBSD, Robert Nagy (robert@) has quietly updated want.html with a request for a new build box for this port:

CVSROOT:	/cvs
Module name:	www
Changes by:	robert@cvs.openbsd.org	2009/02/20 15:45:54

Modified files:
	.              : want.html 

Log message:
A U1 high server with a dual or quad Intel CPU for OpenOffice.Org builds
is needed in Budapest, Hungary. (Unfortunately that's the only size I can
host for free.) I can also receive donations so I can buy such a machine.
Thanks

As you all know, building editors/openoffice3 involves plenty of resources and time. Robert told us that the current build cycle takes over 12 hours which makes the porting process tedious; he also can't afford to keep that build machine running any longer. On a modern quad core CPU machine the build time will be less than half of that, and he can host a 1U rack server for free, thus killing two birds at the same time.

Robert is asking for paypal donations to robert@openbsd.org, so he can purchase such a machine. Considering the money saved in commercial licences because of this port and Robert's work, we hope that the goal can be reached with the help of the community.

(Comments are closed)


Comments
  1. By Anonymous Coward (66.39.160.166) on

    $25@

  2. By Anonymous Coward (80.126.116.76) on

    20 USD from a poor guy

  3. By Blake (82.241.116.109) blake at two one one two dot net on 2112.net

    until you raise enough dough to get the new hardware, are you using ccache to speed up your recompiles?

    -Blake

    Comments
    1. By Anonymous Coward (2a01:348:108:155:216:41ff:fe53:6a45) on

      > until you raise enough dough to get the new hardware, are you using ccache to speed up your recompiles?

      many of the really long really slow bits in OOO are built with rsc, which ccache doesn't help.

      Comments
      1. By tedu (udet) on

        > > until you raise enough dough to get the new hardware, are you using ccache to speed up your recompiles?
        >
        > many of the really long really slow bits in OOO are built with rsc, which ccache doesn't help.

        ok, now i have a perverse need to know, what is rsc? the best i could find is the source, which has the fugliest code style ever seen, inconsistent (possibly incorrect) indentation, and wait for it.... semicolons after braces!

        http://gsl.openoffice.org/source/browse/*checkout*/gsl/rsc/source/rsc/rsc.cxx?rev=1.29

        obviously it's a parser/compiler of some sort, but wtf?

        Comments
        1. By sthen (2a01:348:108:155:216:41ff:fe53:6a45) on

          > > > until you raise enough dough to get the new hardware, are you using ccache to speed up your recompiles?
          > >
          > > many of the really long really slow bits in OOO are built with rsc, which ccache doesn't help.
          >
          > ok, now i have a perverse need to know, what is rsc? the best i could find is the source, which has the fugliest code style ever seen, inconsistent (possibly incorrect) indentation, and wait for it.... semicolons after braces!
          >
          > http://gsl.openoffice.org/source/browse/*checkout*/gsl/rsc/source/rsc/rsc.cxx?rev=1.29
          >
          > obviously it's a parser/compiler of some sort, but wtf?

          there's some sort of description at http://gsl.openoffice.org/:

          - The basic layout of dialogs and the strings that are subject of translation/localization are stored in resource files. The resource compiler creates an efficient binary representation out of a human readable text format.

          from reading this, i don't think you'd possibly imagine it's going to take over an hour on a fast machine.

        2. By Matthias Kilian (91.3.37.138) on

          > [...] and wait for it.... semicolons after braces!

          I've seen this bullshit in some other project (crm114). They refused the patches I sent them, because "semicolons after braces are good". I abandoned my work on a crm114 port the very same day ;-)

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]