From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] sstate.bbclass: check before open the manifest
Date: Fri, 30 Aug 2013 16:29:23 +0100 [thread overview]
Message-ID: <1377876563.1059.100.camel@ted> (raw)
In-Reply-To: <521FF438.5040702@windriver.com>
On Fri, 2013-08-30 at 09:24 +0800, Robert Yang wrote:
>
> On 08/30/2013 01:00 AM, Richard Purdie wrote:
> > On Thu, 2013-08-29 at 09:13 -0400, Robert Yang wrote:
> >> The python stack trace would be printed if we:
> >>
> >> $ bitbake make (the make-3.82 will be built)
> >> // Edit make.inc
> >> $ bitbake make-3.81
> >
> > This is at best hiding the real problem. Why is bitbake building
> > make-3.82 when you asked for make-3.81?
> >
> > I tried this here and also see the warning:
> >
> > ERROR: Multiple .bb files are due to be built which each provide make
> > (/media/build1/poky/meta/recipes-devtools/make/make_3.81.bb /media/build1/poky/meta/recipes-devtools/make/make_3.82.bb).
> > This usually means one provides something the other doesn't and should.
> >
> > so bitbake is basically telling you there is a problem already. So there
> > are two issues:
> >
>
> What I thought was that let the user know the normal error, but we can do
> more to fix it as you pointed out.
>
> > a) Why is make 3.82 being built?
>
> Ah, yes, that's problem, I will do more investigation.
>
> > b) If multiple identical PNs are being built we probably should hard
> > error out since its not supported in the slightest. The sstate race you
> > mention is the least of the problems :(.
> >
>
> OK, I will try to fix such a case:
>
> bitbake make-3.81 make-3.82
I think this should just give an error.
Cheers,
Richard
next prev parent reply other threads:[~2013-08-30 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 13:13 [PATCH 0/1] state.bbclass: check before open the manifest Robert Yang
2013-08-29 13:13 ` [PATCH 1/1] sstate.bbclass: " Robert Yang
2013-08-29 17:00 ` Richard Purdie
2013-08-30 1:24 ` Robert Yang
2013-08-30 15:29 ` Richard Purdie [this message]
2013-08-31 10:51 ` Robert Yang
2013-08-31 22:07 ` Otavio Salvador
2013-09-02 1:59 ` Robert Yang
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=1377876563.1059.100.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox