Re: how to track down parallel build issues?

On Tue, Jun 08, 2010 at 05:57:13PM +0200, Miklos Vajna <[email protected]> wrote:
> Strange, I get a similar error while packaging m19 with -j1 as well.

I did a clean build and now it fails earlier, with a hopefully bit
more meaningful error message:

register component './bridgetest.uno.so' in registry 'uno_services.rdb' succesful!
register component './cppobj.uno.so' in registry 'uno_services.rdb' succesful!
register component './constructors.uno.so' in registry 'uno_services.rdb' succesful!
: &&     LD_LIBRARY_PATH=${LD_LIBRARY_PATH+${LD_LIBRARY_PATH}:}/var/tmp/fst/src/ooo-build-3-2-1-3-16-gc38220b/build/ooo320-m19/solver/320/unxlngi6.pro/lib /var/tmp/fst/src/ooo-build-3-2-1-3-16-gc38220b/build/ooo320-m19/solver/320/unxlngi6.pro/bin/regcomp -register -br ../../unxlngi6.pro/lib/uno_types.rdb -r ../../unxlngi6.pro/lib/uno_services.rdb \
        -c javaloader.uno.so -c javavm.uno.so
javaloader.uno.so
javavm.uno.so
register component 'javaloader.uno.so' in registry '../../unxlngi6.pro/lib/uno_services.rdb' succesful!
register component 'javavm.uno.so' in registry '../../unxlngi6.pro/lib/uno_services.rdb' succesful!
: &&     LD_LIBRARY_PATH=${LD_LIBRARY_PATH+${LD_LIBRARY_PATH}:}/var/tmp/fst/src/ooo-build-3-2-1-3-16-gc38220b/build/ooo320-m19/solver/320/unxlngi6.pro/lib /var/tmp/fst/src/ooo-build-3-2-1-3-16-gc38220b/build/ooo320-m19/solver/320/unxlngi6.pro/bin/regcomp -register  -br ../../unxlngi6.pro/misc/bridgetest/bootstrap.rdb -r ../../unxlngi6.pro/lib/uno_services.rdb -c \
        file:///var/tmp/fst/src/ooo-build-3-2-1-3-16-gc38220b/build/ooo320-m19/testtools/source/bridgetest/../../unxlngi6.pro/class/testComponent.jar \
        -env:URE_INTERNAL_JAVA_DIR=file:///var/tmp/fst/src/ooo-build-3-2-1-3-16-gc38220b/build/ooo320-m19/solver/320/unxlngi6.pro/bin
file:///var/tmp/fst/src/ooo-build-3-2-1-3-16-gc38220b/build/ooo320-m19/testtools/source/bridgetest/../../unxlngi6.pro/class/testComponent.jar
[Java framework] The JRE specified by the bootstrap variable UNO_JAVA_JFW_JREHOME  or  UNO_JAVA_JFW_ENV_JREHOME  could not be recognized. Check the values and make sure that you use a plug-in library that can recognize that JRE.
register component 'file:///var/tmp/fst/src/ooo-build-3-2-1-3-16-gc38220b/build/ooo320-m19/testtools/source/bridgetest/../../unxlngi6.pro/class/testComponent.jar' in registry '../../unxlngi6.pro/lib/uno_services.rdb' failed!
error (RuntimeException): [JavaVirtualMachine]:An unexpected error occurred while starting Java!
using loader com.sun.star.loader.Java2
dmake:  Error code 1, while making '../../unxlngi6.pro/lib/uno_services.rdb'
dmake:  '../../unxlngi6.pro/lib/uno_services.rdb' removed.

ERROR: Error 65280 occurred while making /var/tmp/fst/src/ooo-build-3-2-1-3-16-gc38220b/build/ooo320-m19/testtools/source/bridgetest
rmdir /tmp/GZUkHBnq3H
make: *** [stamp/build] Error 1

Looks like a JVM issue, but the same JVM (gcj-4.5) was used for m17
which built just fine.

Then I did a git log --grep=gcj 167f27d..c38220b and that gave:

commit ab5f47b17d5a8cb773b0b53e2c8adecb8de80de2
Author: Petr Mladek <[email protected]>
Date:   Thu May 20 17:46:12 2010 +0200

    Disabled gcj in supported JRE's (NovellLinuxOnly)
    
    * patches/dev300/jvmfwk-disable-gcj.diff: disable gcj in javavendors_linux.xml;
      OOo newer really worked with it
    * patches/dev300/apply: apply the above diff in NovellLinuxOnly section
    * patches/dev300/build-java-1.4-enable.diff: update to apply

Probably that causes the problem, I'll try with the NovellOnlyUnix
section disabled.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkwPgCkACgkQe81tAgORUJbBzwCfbbv2MWso44HZ5n35Va6IxjLr
8R8Ani+WeAl0BR3IySnyjSibtKCfYopW
=cGDO
-----END PGP SIGNATURE-----