All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Watt <jpewhacker@gmail.com>
To: pawanKumar <pawan4749@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Bitbake failure:
Date: Tue, 27 Mar 2018 09:22:45 -0500	[thread overview]
Message-ID: <1522160565.3242.241.camel@gmail.com> (raw)
In-Reply-To: <CALd6x_s20N1+cW6XmF0BE1g0UnONXq9i+m4_y5hVHg+Cic6gcw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

On Tue, 2018-03-27 at 09:19 +0000, pawanKumar wrote:
> Thanks for your tip.Can I use capital c in place of small c.

Not quite sure what you mean. If you are trying to do:
 bitbake -C fetchall core-image-sato
that doesn't work anymore AFAIK. I don't think there is currently a way
to do a "force invalidate" (e.g. -f) with --runall, although TBH I'm
not sure if 'bitbake -C fetchall' did that anyway. Perhaps someone more
familiar with the recursive dependencies can chime in. 
However, I recently ran into a case where having -f apply to --runall
was useful, so I have a patch in my contrib tree to add support for it.
If that's what you're trying to do, I'm curious what the use case is? I
haven't pushed the patch to the mailing list because I'm not sure if my
use is actually valid.
> On Fri, Mar 23, 2018, 9:20 PM Joshua Watt <jpewhacker@gmail.com>
> wrote:
> > On Fri, 2018-03-23 at 07:31 +0000, pawanKumar wrote:
> > > Hi team,When I tried to run (bitbate -c fetchall) it is giving
> > > error as
> > > "target do_fetchall is not found for image core-image-sato". 
> > > How to over come this error.
> > 
> > I believe fetchall was superseded by --runall. Try:
> > bitbake --runall fetch core-image-sato
> > > Regards
> > > Pavan.

[-- Attachment #2: Type: text/html, Size: 2324 bytes --]

  reply	other threads:[~2018-03-27 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23  7:31 Bitbake failure: pawanKumar
2018-03-23 15:50 ` Joshua Watt
2018-03-27  9:19   ` pawanKumar
2018-03-27 14:22     ` Joshua Watt [this message]
2018-03-28  6:48       ` pawanKumar

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=1522160565.3242.241.camel@gmail.com \
    --to=jpewhacker@gmail.com \
    --cc=pawan4749@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.