Hi,
Thanks for all the advice. I have it built now. After being told about the bitbake -c clean I tried this for the full build, but when it failed I decided to cut my losses and delete tmp and start over.
This succeeded, but I will keep in mind in the future to clean the offending package and rebuilt it and then start the build off again.
I do run using multiple threads and quad core and the built has been successful. I am off to add Qt4 embedded.
Thanks for all the feedback,
Stuart
sakoman wrote:
On Thu, Jul 2, 2009 at 2:17 AM, Elvis Dowson<elvis.dowson@mac.com> wrote:
> it will pick up from where it last left off. This sort of situation
> never used to occur 2-3 months ago, but happens a lot after some
> recent updated to overo-oe.
This issue is not overo specific and occurs in upstream OE too. There
is ongoing discussion there on how to fix it.
I suspect that it will not occur if you disable parallel builds.
Personally I leave parallel builds enabled and just rebuild the
offending packages and restart the build. It only seems to occur on
first or clean builds - once the offending packages are built once you
are usually good to go.
Steve
------------------------------------------------------------------------------
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users
