gcj fails to build OOo 3.1.0 on i386/lpia due to claim that libgcj.spec missing

[Chris Cheney]

Version: 4.4.0-0ubuntu7

gcj-4.4 fails to build OOo 3.1.0 on both i386/lpia but it works fine on amd64.

The error is:

make[1]: Entering directory `/build/buildd/openoffice.org-3.1.0~rc2/debian/tmp/native-jars/gcj'
/usr/bin/gcj -c -g -O2 -fPIC -findirect-dispatch -fjni LuceneHelpWrapper.jar.1.jar -o LuceneHelpWrapper.jar.1.o
/usr/bin/gcj-dbtool -n LuceneHelpWrapper.jar.db 64
gcj: libgcj.spec: No such file or directory
make[1]: *** [LuceneHelpWrapper.jar.1.o] Error 1

However the file is there:

gcj-4.4-jdk: /usr/lib/gcc/i486-linux-gnu/4.4/libgcj.spec

--

amd64 - where it worked
http://launchpadlibrarian.net/26421517/buildlog_ubuntu-karmic-amd64.openoffice.org_1%3A3.1.0~rc2-1ubuntu1_FULLYBUILT.txt.gz

make[1]: Entering directory `/build/buildd/openoffice.org-3.1.0~rc2/debian/tmp/native-jars/gcj'
/usr/bin/gcj -c -g -O2 -fPIC -findirect-dispatch -fjni LuceneHelpWrapper.jar.1.jar -o LuceneHelpWrapper.jar.1.o
/usr/bin/gcj-dbtool -n LuceneHelpWrapper.jar.db 64
/usr/bin/gcj -c -g -O2 -fPIC -findirect-dispatch -fjni ScriptFramework.jar.1.jar -o ScriptFramework.jar.1.o

--

i386 - where it failed
http://launchpadlibrarian.net/26500857/buildlog_ubuntu-karmic-i386.openoffice.org_1%3A3.1.0~rc2-1ubuntu1_FAILEDTOBUILD.txt.gz

make[1]: Entering directory `/build/buildd/openoffice.org-3.1.0~rc2/debian/tmp/native-jars/gcj'
/usr/bin/gcj -c -g -O2 -fPIC -findirect-dispatch -fjni LuceneHelpWrapper.jar.1.jar -o LuceneHelpWrapper.jar.1.o
/usr/bin/gcj-dbtool -n LuceneHelpWrapper.jar.db 64
gcj: libgcj.spec: No such file or directory
make[1]: *** [LuceneHelpWrapper.jar.1.o] Error 1

--

lpia - where it failed
http://launchpadlibrarian.net/26492481/buildlog_ubuntu-karmic-lpia.openoffice.org_1%3A3.1.0~rc2-1ubuntu1_FAILEDTOBUILD.txt.gz

make[1]: Entering directory `/build/buildd/openoffice.org-3.1.0~rc2/debian/tmp/native-jars/gcj'
/usr/bin/gcj -c -g -O2 -fPIC -findirect-dispatch -fjni LuceneHelpWrapper.jar.1.jar -o LuceneHelpWrapper.jar.1.o
/usr/bin/gcj-dbtool -n LuceneHelpWrapper.jar.db 64
gcj: libgcj.spec: No such file or directory
make[1]: *** [LuceneHelpWrapper.jar.1.o] Error 1

--

[Chris Cheney (ccheney)]

To be clear the above commands were run by calling aotcompile.py which is part of libgcj-common.

[Steve Langasek (vorlon)]

The issue is that gcj-4.4 is looking for /usr/lib/gcc/x86_64-linux-gnu/4.4.0/libgcj.spec, whereas libgcj-common, built from the gcc-4.4 source, is shipping it in /usr/lib/gcc/x86_64-linux-gnu/4.4.1/libgcj.spec. Updating gcj-4.4 to a matching upstream version should be enough to fix this problem.

Generally, however, the dependencies should prevent the system from getting into such a state; either gcj-4.4 should have a strict versioned dep on a matching version of libgcj-common, or gcj-4.4 should look for libgcj.spec without the minor version number as part of the path.

[Matthias Klose (doko)]

fixed in gcj-4.4 4.4.0-3ubuntu3

OOo really should use OpenJDK for the build, and just gcj for building the -gcj package.

[Chris Cheney (ccheney)]

Matthias,

That is what OOo is doing... well except in the ia64 case which was switched to gcj due to some bug in openjdk a few months ago. The failure documented above was in the compilation of native jars.

Thanks for fixing it.

Chris

[Chris Cheney (ccheney)]

There was nothing really here to fix for OOo. After the new gcj was uploaded I just had the buildd retry it and it worked.

Thanks,

Chris

[Matthias Klose (doko)]

please change the b-d to openjdk, I really mean it. setting the resolution of this report to invalid is stupid.

[Chris Cheney (ccheney)]

Matthias,

What are you talking about?!?

There is a build-depend on "openjdk-6-jdk [i386 powerpc mips mipsel s390 armel amd64 lpia ppc64]" The only arch it is not set for is ia64 which was done specifically due to a build failure due to openjdk as is documented in the changelog and in the Debian BTS. This particular Ubuntu bug was caused due to openoffice.org also building native jars which uses gcj to do so, I already told you above in this bug report that.

Perhaps you have a reading comprehension problem?

Chris