From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@openembedded.org
Subject: Re: "bitbake -c fetch" and bluez4 warnings?
Date: Sun, 2 Aug 2009 14:49:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0908021448540.2264@localhost> (raw)
In-Reply-To: <b6ebd0a50908021143o515821eaoa78f065043e6a2bf@mail.gmail.com>
On Sun, 2 Aug 2009, Chris Larson wrote:
> -c fetch does the fetch on the providers you request it be run on,
> and only those. base-image has no sources to fetch, so it does
> nothing. If you want to fetch for not just what you're requesting,
> but its dependencies as well, then you want to use -c fetchall.
ah, gotcha. my fault for not reading carefully.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
prev parent reply other threads:[~2009-08-02 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 18:18 "bitbake -c fetch" and bluez4 warnings? Robert P. J. Day
2009-08-02 18:43 ` Chris Larson
2009-08-02 18:49 ` Robert P. J. Day [this message]
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=alpine.LFD.2.00.0908021448540.2264@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 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.