[oe] gcc Recipes

[Richard Purdie]

On Wed, 2010-03-31 at 13:45 +0200, Frans Meulenbroeks wrote:
> I share your feeling of discomfort and depression.
> Personally I feel cleaning up should start with removing obsolete &
> unneeded versions as it is pointless spending time on improving them.
> I've tried to stir up the discussion on cleaning up a few times, and
> gave up due to too much negative feedback and little positive
> feedback.
> But still I wonder what is e.g. the use of recipes like 4.1.1 (which
> btw was released in may 2006).

I don't think removing old versions is going to cut it to be honest as
people are attached to them for various reasons. Having them around
isn't really a problem, I'm more concerned about the general sprawl of
the recipes which makes them hard to understand. Its clear some are more
broken than others.

> Having said that:
> I've looked at your commit. Looks fine to me so a +1 & thumbs up.
>
> PS: not sure about all the variants, but it might be nice to be able
> to use something like BBCLASSEXTEND="cross".
> Don't think my pythonese and knowledge of the gcc build system is good
> enough to cook up something though.

Well, the variants are ugly but before we can thing about doing anything
about them using BBCLASSEXTEND they have to be condensed down to:

require gcc_${PV}.bb
inherit someclass

This is another reason to try and focus the details into one place as
perhaps then we'll be able to achieve something like this. Even if we
don't use BBCLASSEXTEND, making large numbers of the files simple boiler
plate will make it easier to understand.

Cheers,

Richard