ftbfs on all !x86 archs

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, , because your description didn't include enough information.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
4. the version of Ubuntu you are using.
5. please attach a copy of your build log, so as much information as possible is available.
Thanks!

Charlie, build failures do not require more information from the submitter.

Hi,
this is the output on an up-to-date intrepid. So i have the same effect as before the beta release.
I hope this helps you.

sudo aptitude install openoffice.org
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut
Lese Status-Informationen ein... Fertig
Reading extended state information
Initializing package states... Fertig
The following packages are BROKEN:
  openoffice.org-core
The following NEW packages will be installed:
  bsh{a} bsh-gcj{a} default-jre-headless{a} fastjar{a} gcj-4.3-base{a}
  gij-4.3{a} java-common{a} java-gcj-compat{a} java-gcj-compat-headless{a}
  libbcel-java{a} libgcj-bc{a} libgcj-common{a} libgcj9-0{a}
  libgcj9-0-awt{a} libgcj9-jar{a} libjaxp1.3-java{a} libjaxp1.3-java-gcj{a}
  libjline-java{a} liblog4j1.2-java{a} liblog4j1.2-java-gcj{a}
  libmx4j-java{a} libneon27{a} libregexp-java{a} libwpg-0.1-1{a}
  libwps-0.1-1{a} libxalan2-java{a} libxalan2-java-gcj{a}
  libxerces2-java{a} libxerces2-java-gcj{a} openoffice.org
  openoffice.org-base{a} openoffice.org-base-core{a} openoffice.org-calc{a}
  openoffice.org-common{a} openoffice.org-draw{a}
  openoffice.org-filter-binfilter{a} openoffice.org-filter-mobiledev{a}
  openoffice.org-impress{a} openoffice.org-java-common{a}
  openoffice.org-math{a} openoffice.org-style-human{a}
  openoffice.org-writer{a} python-uno{a} ttf-dejavu{a} ttf-dejavu-extra{a}
  ttf-opensymbol{a}
0 packages upgraded, 47 newly installed, 0 to remove and 2 not upgraded.
Need to get 96,1MB of archives. After unpacking 346MB will be used.
The following packages have unmet dependencies:
  openoffice.org-core: Hängt ab: libhunspell-1.1-0 (>= 1.1.6-1) which is a virtu
al package.
The following actions will resolve these dependencies:

Keep the following packages at their current version:
openoffice.org [Not Installed]
openoffice.org-base [Not Installed]
openoffice.org-calc [Not Installed]
openoffice.org-common [Not Installed]
openoffice.org-core [Not Installed]
openoffice.org-draw [Not Installed]
openoffice.org-filter-binfilter [Not Installed]
openoffice.org-filter-mobiledev [Not Installed]
openoffice.org-impress [Not Installed]
openoffice.org-java-common [Not Installed]
openoffice.org-math [Not Installed]
openoffice.org-style-human [Not Installed]
openoffice.org-writer [Not Installed]
python-uno [Not Installed]

Score is -9764

Accept this solution? [Y/n/q/?]

Marking as critical for the PS3 Port as this prevents successful installation.

Looking through the log for the failed powerpc build of 1:2.4.1-9ubuntu2 [0] there are now two issues reported (from line 175339):

<snippet>
2 module(s):
 bean
 testtools
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /build/buildd/openoffice.org-2.4.1/ooo-build/build/OOH680_m17/bean/native/unix
ERROR: error 65280 occurred while making /build/buildd/openoffice.org-2.4.1/ooo-build/build/OOH680_m17/testtools/source/bridgetest
</snippet>

1) BEAN

The "bean" module failure is as Steve noted above - some sort of linking error relating to libjawt (from line 61621):

<snippet>
Making: ../../unxlngppc.pro/lib/libofficebean.so
powerpc-linux-gnu-g++ -Wl,-rpath,'$ORIGIN:$ORIGIN/../ure-link/lib' -shared -L../../unxlngppc.pro/lib -L../lib -L/build/buildd/openoffice.org-2.4.1/ooo-build/build/OOH680_m17/solenv/unxlngppc/lib -L/build/buildd/openoffice.org-2.4.1/ooo-build/build/OOH680_m17/solver/680/unxlngppc.pro/lib -L/build/buildd/openoffice.org-2.4.1/ooo-build/build/OOH680_m17/solenv/unxlngppc/lib -L/usr/lib/jvm/default-java/lib -L/usr/lib/jvm/default-java/jre/bin -L/usr/lib/jvm/default-java/jre/bin/classic -L/usr/lib/jvm/default-java/jre/bin -L/usr/lib -L/usr/lib/xulrunner-devel-1.9.0.3/sdk/lib ../../unxlngppc.pro/slo/officebean_version.o -o ../../unxlngppc.pro/lib/libofficebean.so ../../unxlngppc.pro/slo/com_sun_star_comp_beans_LocalOfficeWindow.o ../../unxlngppc.pro/slo/com_sun_star_beans_LocalOfficeWindow.o -ljawt -lstdc++ -ldl -lpthread -lm
/usr/bin/ld: cannot find -ljawt
collect2: ld returned 1 exit status
dmake: Error code 1, while making '../../unxlngppc.pro/lib/libofficebean.so'
</snippet>

2) TESTTOOLS

I believe the second failure in the "testtools" module is this (from line 68355):

<snippet>
regcomp -register -br ../../unxlngppc.pro/misc/bridgetest/bootstrap.rdb -r ../../unxlngppc.pro/lib/uno_services.rdb -c \
        file:///build/buildd/openoffice.org-2.4.1/ooo-build/build/OOH680_m17/testtools/source/bridgetest/../../unxlngppc.pro/class/testComponent.jar \
        -env:URE_INTERNAL_JAVA_DIR=file:///build/buildd/openoffice.org-2.4.1/ooo-build/build/OOH680_m17/solver/680/unxlngppc.pro/bin
file:///build/buildd/openoffice.org-2.4.1/ooo-build/build/OOH680_m17/testtools/source/bridgetest/../../unxlngppc.pro/class/testComponent.jar
using loader com.sun.star.loader.Java2
LOG: [0x40031bc0] exception thrown while VM is initializing:
LOG: [0x40031bc0] NULL: java.lang.Object
LOG: [0x40031bc0] Aborting...
dmake: Error code 134, while making '../../unxlngppc.pro/lib/uno_services.rdb'
dmake: '../../unxlngppc.pro/lib/uno_services.rdb' removed.
</snippet>

There is another error a little before this one which may/may not be related because it's marked as "Ignored" by the build system (from line 67369):

<snippet>
out ../../../unxlngppc.pro/bin/cli_types_bridgetest.dll -r /build/buildd/openoffice.org-2.4.1/ooo-build/build/OOH680_m17/solver/680/unxlngppc.pro/bin/cli_types.dll \
  -X /build/buildd/openoffice.org-2.4.1/ooo-build/build/OOH680_m17/solver/680/unxlngppc.pro/bin/types.rdb ../../../unxlngppc.pro/bin/bridgetest.rdb
dmake: Error executing 'out': No such file or directory (Ignored)
</snippet>

[0] https://launchpad...

Re the "bean" module build fail. It appears the library search path is wrong. This is the build command used:

powerpc-linux-gnu-g++
 -Wl,-rpath,'$ORIGIN:$ORIGIN/../ure-link/lib'
 -shared
 -L../../unxlngppc.pro/lib
 -L../lib
 -L/build/buildd/openoffice.org-2.4.1/ooo-build/build/OOH680_m17/solenv/unxlngppc/lib
 -L/build/buildd/openoffice.org-2.4.1/ooo-build/build/OOH680_m17/solver/680/unxlngppc.pro/lib
 -L/build/buildd/openoffice.org-2.4.1/ooo-build/build/OOH680_m17/solenv/unxlngppc/lib
 -L/usr/lib/jvm/default-java/lib
 -L/usr/lib/jvm/default-java/jre/bin
 -L/usr/lib/jvm/default-java/jre/bin/classic
 -L/usr/lib/jvm/default-java/jre/bin
 -L/usr/lib
 -L/usr/lib/xulrunner-devel-1.9.0.3/sdk/lib ../../unxlngppc.pro/slo/officebean_version.o
 -o ../../unxlngppc.pro/lib/libofficebean.so ../../unxlngppc.pro/slo/com_sun_star_comp_beans_LocalOfficeWindow.o ../../unxlngppc.pro/slo/com_sun_star_beans_LocalOfficeWindow.o
 -ljawt
 -lstdc++
 -ldl
 -lpthread
 -lm

As default-jdk-builddep currently resolves to the cacao packages it should be using /usr/lib/jvm/default-java/jre/lib/ppc/ not /usr/lib/jvm/default-java/jre/bin/classic. I've been hunting through the source like mad tonight. I don't believe these paths are configured anywhere in debian/rules. So the settings must be somewhere in ooo-build or ooo-build/src/*.tar.bzr. Not located as yet.

If anyone watching can nudge me in the right direction here that would be greatly appreciated. Otherwise will continue tomorrow.

Ok I think I found the file we'd need to fix to get this to build using Cacoa on powerpc. However, looking at the debian bug tracker ...

#495694 "doesn't work with cacao as JVM" (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495694)

... I'm not sure it'd be worth fixing this if we're only going to uncover yet more install or usage problems. At this late stage I'm rather more concerned to have an installable system on powerpc and at least a partially working OOo. So could we consider:

a) Switching to gcj for powerpc?
b) Disabling Java in OOo for powerpc?

Cheers

Dan

This bug was fixed in the package openoffice.org - 1:2.4.1-11ubuntu1

---------------
openoffice.org (1:2.4.1-11ubuntu1) intrepid; urgency=low

  * Resynchronise with Debian (r1195). Remaining changes:
    - Add Launchpad integration support.
    - Add Launchpad translations support.
    - Add package openoffice.org-style-human.
    - Add some Ubuntu-specific bitmaps. Adjust broffice diversions for these.
    - Add path to OOo SDK wrapper script.
    - Add suggests gstreamer to openoffice.org-impress.
    - Add support for compressing debs with lzma.
    - Add support for openjdk-6.
    - Add support for shared /usr/share/doc directories.
    - Add support to build l10n as a separate source.
    - Add support to build on lpia.
    - Add support to turn off building on sparc.
    - Add Xb-Npp-xxx tags according to "firefox distro add-on suport" spec.
    - Set template.desktop to not display in the menu.
    - Use imagemagick instead of graphicsmagick.
  * Resynchronise with ooo-build-2-4-1 (r14314).
  * Add ooo-build/patches/src680/config_office-openjdk-paths.diff to correct
    java build problems. Closes LP: #273268
  * Add shared-mime-info mimetype file. Closes LP: #228770
  * Add support for abrowser. Closes LP: #272772
  * Disable java on powerpc due to cacao being broken.
  * Merge debian-2-4-1 changes into ooo-build-2-4-1.

 -- Chris Cheney <email address hidden> Tue, 14 Oct 2008 23:55:39 -0500

So while the actual OOo packages now build, they don't actually work and bomb out with a broken depends on openoffice.org-report-builder-bin. Now what?

We could drop the dependency in the control file, but that seems like a bad idea, especially if this could be fixed.

Michael,

Which part doesn't work other than report-builder? report-builder is an arch all package which is why it exists even though powerpc doesn't have java support. I can see if it is possible to completely disabling report-builder from being available for powerpc in the next release.

with openoffice 2.4 you have to update all your sistem. for that work very well

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!