Hi.

Matthijs van de Water schrieb:
> 2) Split out all GCJ related stuff to compile in a separate set of
> tasks so that it does not always get build, because this takes ages
> and loads of memory.
I don't think that is possible atm. GCJ is part of a GCC build and can
only be enabled or disabled at configuration time.

I did a quick glance at the gcc-package-*.inc recipes and they do not
provide packaging info for GCJ specifically. So either things end up
in another binary package or they end up nowhere. I'll have a look at that.

> I'm not sure about the best way to get (2)... any suggestions are welcome.
> 
> Regards,
> Matthijs
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>