All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Stefan Stanacar <sstncr@gmail.com>
Cc: yocto@yoctoproject.org, gary@mlbassoc.com
Subject: Re: meta-mono core-image-mono failing
Date: Thu, 22 May 2014 00:23:12 +0100	[thread overview]
Message-ID: <537D3560.2040702@dynamicdevices.co.uk> (raw)
In-Reply-To: <CANr+NRsnNeBtkJOB-EVNzsGWOOH6YG1cnw11FOcbo9V78-8vPg@mail.gmail.com>

>
> 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
 


  reply	other threads:[~2014-05-21 23:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 18:25 meta-mono core-image-mono failing Chris Morgan
2014-05-21 18:57 ` Gary Thomas
2014-05-21 19:07   ` Chris Morgan
2014-05-21 20:15     ` Alex J Lennon
2014-05-21 20:26       ` Chris Morgan
2014-05-21 20:35         ` Alex J Lennon
2014-05-21 22:28           ` Chris Morgan
2014-05-22  7:59         ` Alex J Lennon
2014-05-21 23:10       ` Stefan Stanacar
2014-05-21 23:23         ` Alex J Lennon [this message]
2014-05-22  8:23           ` Richard Purdie
2014-05-22  8:29             ` Alex J Lennon
2014-05-22  8:40               ` Richard Purdie
2014-05-22  9:56                 ` Alex J Lennon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=537D3560.2040702@dynamicdevices.co.uk \
    --to=ajlennon@dynamicdevices.co.uk \
    --cc=gary@mlbassoc.com \
    --cc=sstncr@gmail.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.