Re: how to track down parallel build issues?

On Thu, Jun 10, 2010 at 12:06:30PM +0200, Petr Mladek <[email protected]> wrote:
> Miklos Vajna píše v St 09. 06. 2010 v 13:51 +0200:
> > 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.
> 
> Grr, I am really sorry for the troubles. I have missed the fact that
> this section is used by other distros.

Build just finished, so yes, that caused the problem.

> If this is the problem and you would want to use the other
> NovellOnlyUnix diffs, we could move the jvmfwk-disable-gcj.diff to a
> special section and enable it really only for Novel Linux distros.

Thanks, though I think I can just remove NovellOnlyUnix from Frugalware,
after all the name already suggests not using it on other distros. ;)

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

iEYEARECAAYFAkwQwsYACgkQe81tAgORUJbP1wCeJBzbSsjxi0eQuttAMQDM2KZ+
68EAoKGSFAZ1ZmqDCjRVw/R1MkGaM51p
=GqaB
-----END PGP SIGNATURE-----