Why doesn't my package rebuild
Sort of as a follow up to my problem of yesterday, I've run into a problem - I have a simple recipe which only unpacks a source tarball and then installs it - no other steps are listed or required. The recipe also does not have an explicit PR value and I'm not running a PR server.
If I have the package built, then change the tarball and the checksums in the recipe itself, it does not get rebuilt :-( I have to force it using cleansstate.
This setup seems to work fine for my other recipes. I just tried it with two nearly identical recipes. I made similar changes in both recipes/files - one was rebuilt, the other not.
How can I diagnose this? It's a private recipe (no use to anyone but me) so I'm not going to send it to the list but I can gladly share it with anyone who might be able to help.
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 9 lines · Gary Thomas
Sort of as a follow up to my problem of yesterday, I've run into a problem - I have a simple recipe which only unpacks a source tarball and then installs it - no other steps are listed or required. The recipe also does not have an explicit PR value and I'm not running a PR server.
If I have the package built, then change the tarball and the checksums in the recipe itself, it does not get rebuilt :-( I have to force it using cleansstate.
Quoted 7 lines
This setup seems to work fine for my other recipes. I just tried it with two nearly identical recipes. I made similar changes in both recipes/files - one was rebuilt, the other not.
How can I diagnose this? It's a private recipe (no use to anyone but me) so I'm not going to send it to the list but I can gladly share it with anyone who might be able to help.
Hi Gary,
You can increase the Debug level for your build with bitbake -D. You can specify this more than once for additional output, example: -DDD. This may help you to diagnose what's going on.
Quoted 13 lines
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Quoted 18 lines · William M.A. Traynor
Quoted 9 lines · Gary Thomas
Sort of as a follow up to my problem of yesterday, I've run into a problem - I have a simple recipe which only unpacks a source tarball and then installs it - no other steps are listed or required. The recipe also does not have an explicit PR value and I'm not running a PR server.
If I have the package built, then change the tarball and the checksums in the recipe itself, it does not get rebuilt :-( I have to force it using cleansstate.
Quoted 7 lines
This setup seems to work fine for my other recipes. I just tried it with two nearly identical recipes. I made similar changes in both recipes/files - one was rebuilt, the other not.
How can I diagnose this? It's a private recipe (no use to anyone but me) so I'm not going to send it to the list but I can gladly share it with anyone who might be able to help.
Quoted 5 lines
Hi Gary,
You can increase the Debug level for your build with bitbake -D. You can specify this more than once for additional output, example: -DDD. This may help you to diagnose what's going on.
Thanks, that was the hint I was looking for.
Of course, today the recipe behaves... At least I'll know what to do the next time I have problems.
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------