<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -159,16 +159,32 @@ Module 'packimages' delivered successfully. 6 files copied, 2 files unchanged
 Build succeeded ...!
 touch stamp/build
 
+... creating preregistered services.rdb ...
 
-... analyzing files ...
-ERROR: The following files could not be found: 
-ERROR: File not found: instooofiltmsi.dll
-ERROR: File not found: libstlport_gcc.dll
-ERROR: File not found: shlxtmsi.dll
+**************************************************
+ERROR: ERROR: Could not register all components for file services.rdb (gid_Starr
+egistry_Services_Rdb)!
+in function: create_services_rdb
+**************************************************
+
+**************************************************
+ERROR: Saved logfile: /home/janneke/vc/gub/target/mingw/build/openoffice-trunk/b
+uild/ooo300-m9/instsetoo_native/util/OpenOffice//logging/en-US/log_OOO300_en-US.
+log
+**************************************************
 ... cleaning the output tree ...
-Wed Nov 26 22:57:02 2008 (00:10 min.)
+... removing directory /home/janneke/vc/gub/target/mingw/build/openoffice-trunk/
+build/ooo300-m9/instsetoo_native/util/OpenOffice//zip/en-US ...
+... removing directory /home/janneke/vc/gub/target/mingw/build/openoffice-trunk/
+build/ooo300-m9/instsetoo_native/util/OpenOffice//gid_Starregistry_Services_Rdb_
+servicesrdb/en-US_witherror_1 ...
+Thu Feb 19 14:30:56 2009 (01:23 min.)
 Failed to install:  at ./ooinstall line 143.
-make: *** [install] Fout 1
+make: *** [install] Error 1
+
+Saved logs at:
+
+    http://lilypond.org/~janneke/software/ooo/gub-mingw/
 
 '''
 
@@ -417,6 +433,14 @@ LD_LIBRARY_PATH=%(LD_LIBRARY_PATH)s
 ''')
 ##main configure barfs
 ##CPPFLAGS=
+    def install (self):
+        self.system ('''
+cd %(upstream_dir)s/cppuhelper &amp;&amp; rm -rf wntgcci.pro-
+cd %(upstream_dir)s/cppuhelper &amp;&amp; mv wntgcci.pro wntgcci.pro-
+cd %(upstream_dir)s/cppuhelper &amp;&amp; . ../Linux*.sh &amp;&amp; perl $SOLARENV/bin/build.pl  &amp;&amp; debug=true &amp;&amp; perl $SOLARENV/bin/deliver.pl
+''')
+        target.AutoBuild.install (self)
+        
                 
 class Openoffice__mingw (Openoffice):
     upstream_patches = Openoffice.upstream_patches + ['openoffice-config_office-mingw.patch', 'openoffice-solenv-mingw.patch', 'openoffice-sal-mingw.patch', 'openoffice-external-mingwheaders.patch', 'openoffice-cppunit-mingw.patch', 'openoffice-i18npool-mingw.patch', 'openoffice-tools-mingw.patch', 'openoffice-setup_native-mingw.patch', 'openoffice-pyuno-mingw.patch', 'openoffice-sysui-mingw.patch', 'openoffice-dtrans-mingw.patch', 'openoffice-fpicker-mingw.patch', 'openoffice-sccomp-mingw.patch', 'openoffice-vcl-mingw.patch', 'openoffice-connectivity-mingw.patch', 'openoffice-unotools-mingw.patch', 'openoffice-embeddedobj-mingw.patch', 'openoffice-shell-mingw.patch', 'openoffice-svx-mingw.patch', 'openoffice-dbaccess-mingw.patch', 'openoffice-desktop-mingw.patch', 'openoffice-scripting-mingw.patch', 'openoffice-postprocess-mingw.patch', 'openoffice-instsetoo_native-mingw.patch', 'openoffice-solenv-mingw-installer.patch', 'openoffice-scp2-mingw.patch']</diff>
      <filename>gub/specs/openoffice.py</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>08e80e07d90bc97216f2b1470fea902e32135470</id>
    </parent>
  </parents>
  <author>
    <name>Jan Nieuwenhuizen</name>
    <email>janneke@gnu.org</email>
  </author>
  <url>http://github.com/janneke/gub/commit/572b59b05a826fe16d0c7cca1200a7200febf679</url>
  <id>572b59b05a826fe16d0c7cca1200a7200febf679</id>
  <committed-date>2009-02-20T06:01:20-08:00</committed-date>
  <authored-date>2009-02-20T06:01:20-08:00</authored-date>
  <message>OpenOffice: build cppuhelper with debug=true.

This should print actual reasons why the install fails.

[It still puzzles me why OpenOffice.org's build and install system
will more often than not just abort without giving the reason of
failure.  Does it only fail for me?  Am I misinformed?  Am I too dense
to interpret the --mostly-- constant error messages?  Are there so
many places of failure that people are too discouraged to fix it?  Is
it slated for a rewrite?  Is making a small fix in ooo-build not worth
it because it won't be upstreamed, and is upstreaming a small fix not
worth the hassle?  Does noone (at upstream) use it?]  confused /me</message>
  <tree>5217ad4139db5c8c65dd342f1177df51b551ef43</tree>
  <committer>
    <name>Jan Nieuwenhuizen</name>
    <email>janneke@gnu.org</email>
  </committer>
</commit>
