[yocto] meta-mono core-image-mono failing

[Alex J Lennon]

>
> The reason you don't see this is because you are building on daisy,
> but Chris is building on master. I doubt it it has something to do
> with the host distro.
> Specifically master enables separate build dir by default in
> autotools.bbclass whereas daisy doesn't.
>
> Daisy has these:
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=daisy&id=bf33e93f162c9fbba079b4de01c35dcb367c0577
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=daisy&id=069de520ec864fc78084e8f1ddfb20edaab55f5e
>
> which enable only the core recipes and then marks the broken ones, but
> master has one more:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=69b6eaca3d9b635e8a61a0fdbd814b558e91901d
>
>
> which breaks other layers with recipes that don't work with B!=S and
> they should either get fixed or use autotools-brokensep, so I guess
> Chris's patch is the way to go for now...
>
> Cheers,
> Stefan
>

Thanks Stefan.  > daisy was my suspicion but that seemed unlikely so I
have a clean Fedora build underway with daisy / meta-mono /
core-image-mono to prove it to myself as a first pass before trying master.

As I do this I am thinking it would be nice if there were canonical
images of Yocto-X.Y available to run up on Amazon/Azure/elsewhere to
prove these things out in the background without mashing my SSDs.

I am guessing somebody has done this already but I hunted around Amazon
and couldn't see any community images that looked useful (?)

Similarly (and I confess I haven't yet had time to understand
AutoBuilder as I should) presumably there are a number of daily builds
in the cloud, on each of the supported host platforms, for each of the
advertised layers, and if they fail then maintainers are kicked? Is that
how things work? If so, can you advise how I request to add meta-mono to
the kick-list?

Cheers,

Alex