From: Darren Hart <dvhart@linux.intel.com>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: yocto@yoctoproject.org
Subject: Re: This one can't be me...
Date: Wed, 03 Apr 2013 15:09:14 -0700 [thread overview]
Message-ID: <515CA88A.9080806@linux.intel.com> (raw)
In-Reply-To: <80CD287EE4364CEF8862D95048BCA9A9@PAULD>
On 04/03/2013 01:50 PM, Paul D. DeRocco wrote:
>> From: Darren Hart [mailto:dvhart@linux.intel.com]
>>
>> Are you building with the rm work setting? Otherwise, that
>> should not be
>> empty unless you have more than one linux-yocto* directory
>> and the other is populated.
>
> That option is off, and there is no other linux-yocto* directory.
>
>> If not, verify rm work is not on and just build the kernel:
>>
>> $ bitbake linux-yocto -c cleansstate
>> $ bitbake linux-yocto
>
> The first line says there is no do_cleanstate task for linux-yocto, and so
> the second line finds nothing to do. Is there another way to force that?
This doesn't make any sense. Can you send the actual output rather than
interpreting please?
Oh, actually, please read the command more carefully, there are two ss's in
cleansstate.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2013-04-03 22:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 21:27 This one can't be me Paul D. DeRocco
2013-04-02 23:57 ` Paul D. DeRocco
2013-04-03 16:04 ` Marc Ferland
2013-04-03 15:38 ` Darren Hart
2013-04-03 17:47 ` Bodke, Kishore K
2013-04-03 19:57 ` Paul D. DeRocco
2013-04-03 20:24 ` Darren Hart
2013-04-03 20:50 ` Paul D. DeRocco
2013-04-03 22:01 ` Bodke, Kishore K
2013-04-04 0:32 ` Paul D. DeRocco
2013-04-04 17:17 ` Darren Hart
2013-04-03 22:09 ` Darren Hart [this message]
2013-04-04 0:21 ` Paul D. DeRocco
2013-04-04 17:18 ` Darren Hart
2013-04-04 18:31 ` Bodke, Kishore K
2013-04-04 19:14 ` Bodke, Kishore K
2013-06-20 14:58 ` Darren Hart
[not found] ` <13F417252F8B4CB5BB755BB07928D20C@PAULD>
[not found] ` <D956029D25CF204F948EA0FB515E1EE258405AC4@ORSMSX105.amr.corp.intel.com>
[not found] ` <2FD1BA69DE1E491C839CA26A7D2CA32A@PAULD>
[not found] ` <D956029D25CF204F948EA0FB515E1EE258405C96@ORSMSX105.amr.corp.intel.com>
2013-04-05 17:06 ` Paul D. DeRocco
2013-04-05 18:15 ` Bodke, Kishore K
2013-04-05 18:48 ` Paul D. DeRocco
2013-04-05 22:32 ` Bodke, Kishore K
2013-04-05 22:45 ` Paul D. DeRocco
2013-04-05 23:17 ` Sean Liming
2013-04-05 23:54 ` Paul D. DeRocco
2013-04-05 23:34 ` Tom Zanussi
2013-04-06 4:03 ` Tom Zanussi
2013-04-06 4:15 ` Paul D. DeRocco
2013-04-06 4:48 ` Tom Zanussi
2013-04-06 5:55 ` Bruce Ashfield
2013-04-06 14:00 ` Tom Zanussi
2013-04-06 18:20 ` Paul D. DeRocco
2013-04-06 19:20 ` Tom Zanussi
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=515CA88A.9080806@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=pderocco@ix.netcom.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.