bitbake clean / cleanall / cleansstate not working

bitbake clean / cleanall / cleansstate not working

[Purcareata Bogdan-B43198]

Hello,

I am using Yocto with BB_VERSION = "1.18.0" and the commands in the subject do not seem to work - they don't do anything. The image has the packages built.

$ bitbake -c cleanall gcc
[ ... ]
NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and all succeeded.

$ bitbake -c clean gcc
[ ... ]
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and all succeeded.

$ bitbake -c cleansstate gcc
[ ... ]
NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and all succeeded.

The information in [ ... ] is not really relevant. I just wanted to give the output message. I know the error description is vague, but so is this behavior. I don't know what it could be further related to.

Thank you very much,
Bogdan P.

Re: bitbake clean / cleanall / cleansstate not working

[Richard Purdie]

On Wed, 2013-04-17 at 09:42 +0000, Purcareata Bogdan-B43198 wrote:
> Hello,
> 
> I am using Yocto with BB_VERSION = "1.18.0" and the commands in the subject do not seem to work - they don't do anything. The image has the packages built.
> 
> $ bitbake -c cleanall gcc
> [ ... ]
> NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and all succeeded.
> 
> $ bitbake -c clean gcc
> [ ... ]
> NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and all succeeded.
> 
> $ bitbake -c cleansstate gcc
> [ ... ]
> NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and all succeeded.
> 
> The information in [ ... ] is not really relevant. I just wanted to
> give the output message. I know the error description is vague, but so
> is this behavior. I don't know what it could be further related to.

What exactly are you trying to clean? The above messages say it ran 1, 2
or 3 tasks and they all succeeded.

Keep in mind there are several "gcc" components such as gcc-cross,
gcc-cross-initial and so on. "gcc" is the one used on target.

Cheers,

Richard

Re: bitbake clean / cleanall / cleansstate not working

[Purcareata Bogdan-B43198]

Bogdan P.

> -----Original Message-----
> From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org]
> Sent: Saturday, April 20, 2013 10:40 AM
> To: Purcareata Bogdan-B43198
> Cc: bitbake-devel@lists.openembedded.org
> Subject: Re: [bitbake-devel] bitbake clean / cleanall / cleansstate not working
> 
> On Wed, 2013-04-17 at 09:42 +0000, Purcareata Bogdan-B43198 wrote:
> > Hello,
> >
> > I am using Yocto with BB_VERSION = "1.18.0" and the commands in the subject do not seem to work -
> they don't do anything. The image has the packages built.
> >
> > $ bitbake -c cleanall gcc
> > [ ... ]
> > NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and all succeeded.
> >
> > $ bitbake -c clean gcc
> > [ ... ]
> > NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and all succeeded.
> >
> > $ bitbake -c cleansstate gcc
> > [ ... ]
> > NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and all succeeded.
> >
> > The information in [ ... ] is not really relevant. I just wanted to
> > give the output message. I know the error description is vague, but so
> > is this behavior. I don't know what it could be further related to.
> 
> What exactly are you trying to clean? The above messages say it ran 1, 2
> or 3 tasks and they all succeeded.

In my example, "gcc" can be replaced with any package provided by the Yocto recipes.
The problem is that nothing is being run - "0 didn't need to be rerun " - so the built package is never cleaned.
This issue is present when running all clean commands - clean, cleanall, cleansstate.

> 
> Keep in mind there are several "gcc" components such as gcc-cross,
> gcc-cross-initial and so on. "gcc" is the one used on target.

Do you think that a certain package can't be cleaned because of its dependencies?

> 
> Cheers,
> 
> Richard
> 

Re: bitbake clean / cleanall / cleansstate not working

[Paul Eggleton]

On Monday 22 April 2013 09:42:07 Purcareata Bogdan-B43198 wrote:
> Richard Purdie wrote:
> > What exactly are you trying to clean? The above messages say it ran 1, 2
> > or 3 tasks and they all succeeded.
> 
> In my example, "gcc" can be replaced with any package provided by the Yocto
> recipes. The problem is that nothing is being run - "0 didn't need to be
> rerun " - so the built package is never cleaned. This issue is present when
> running all clean commands - clean, cleanall, cleansstate.

"0 didn't need to be rerun" does not mean nothing was done - it means the 
opposite. The number reported here is the number of tasks that were able to be 
restored from shared state - none (0) in this case because this is not 
applicable to the clean* tasks.

Other than the message above, how are you determining that these tasks are not 
doing anything?

> > Keep in mind there are several "gcc" components such as gcc-cross,
> > gcc-cross-initial and so on. "gcc" is the one used on target.
> 
> Do you think that a certain package can't be cleaned because of its
> dependencies?

No, that's very unlikely to be the case.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: bitbake clean / cleanall / cleansstate not working

[Purcareata Bogdan-B43198]

On 4/22/2013 2:05 PM, Paul Eggleton wrote:
> On Monday 22 April 2013 09:42:07 Purcareata Bogdan-B43198 wrote:
>> Richard Purdie wrote:
>>> What exactly are you trying to clean? The above messages say it ran 1, 2
>>> or 3 tasks and they all succeeded.
>> In my example, "gcc" can be replaced with any package provided by the Yocto
>> recipes. The problem is that nothing is being run - "0 didn't need to be
>> rerun " - so the built package is never cleaned. This issue is present when
>> running all clean commands - clean, cleanall, cleansstate.
> "0 didn't need to be rerun" does not mean nothing was done - it means the
> opposite. The number reported here is the number of tasks that were able to be
> restored from shared state - none (0) in this case because this is not
> applicable to the clean* tasks.
>
> Other than the message above, how are you determining that these tasks are not
> doing anything?

Thank you for the fast reply!

I've run some more tests and found some new stuff.

I'm running this:
     bitbake <package>
     bitbake -c cleanall <package>
     bitbake <package>

My expected result was that, at the second run of bitbake <package>, the 
whole package will be built again starting from fetch. While this is 
true for packages such as gcc or busybox, it's not true for the lxc 
package - this one starts from do_populate_sysroot (or somewhere near, I 
can't seem to tell since it's running very fast). I discovered this 
while developing some patches for the lxc recipe. I was hoping to see 
the functionality applied after clean and build, but it was not there.

When I saw "0 didn't need to be rerun " after bitbake cleanall, I 
thought it didn't run anything - now I understand what it means. I 
noticed this behavior for other packages as well, so I didn't bother to 
build the packages after clean, since I thought cleaning was the problem.

Do you think this behavior is recipe dependent?

>
>>> Keep in mind there are several "gcc" components such as gcc-cross,
>>> gcc-cross-initial and so on. "gcc" is the one used on target.
>> Do you think that a certain package can't be cleaned because of its
>> dependencies?
> No, that's very unlikely to be the case.
>
> Cheers,
> Paul
>