Re: build error after recent pull
On 03/19/2012 05:27 PM, Gary Thomas wrote:
On 2012-03-19 14:49, jfabernathy wrote:I never got a complete good build after I updated some unknown items in Ubuntu 11.10 dev system and did a recent git pull until I did a completely new bitbake core-image-sato to a new build directory. That completed correctly.On 03/19/2012 04:25 PM, Gary Thomas wrote:These errors should not happen - you should be able to update theOn 2012-03-19 13:25, jfabernathy wrote:After I fixed mesa-dri and started bitbake core-image-sato, it ran for a long time and had a build failure similar to the first one on kexec-tools. I did the bitbake -c cleansstateOn 03/19/2012 03:13 PM, Gary Thomas wrote:If you run just 'bitbake core-image-sato', any packages (recipes)On 2012-03-19 13:04, jfabernathy wrote:No to question on rm_work in local.confOn 03/19/2012 03:03 PM, Gary Thomas wrote:Do you have rm_work in your local.conf?On 2012-03-19 12:59, jfabernathy wrote:I had a preview successful build and just reran that after bitbake -c cleanall core-image-satoOn 03/19/2012 02:55 PM, Gary Thomas wrote:Was your build from scratch? Do you use [extant] sstate cache?On 2012-03-19 10:02, jfabernathy wrote:Building on latest release Ubuntu 11.10 (Linux ubuntu-x64 3.0.0-16-generic #29-Ubuntu SMP)Just did a git pull today on poky and meta-intel. I tried to rebuild meta-sugarbay again and got a build error. Not sure why yet. Not critical, just a spot check of things.What's your build host?
So it seems we may need some Rules for users to follow when rebuilding with the latest versions of Yocto. It seems there are some dependency on certain key packages on the dev system not changing. Completely rebuilding seems to be the safest method and given the time wasted when things fail, might be the fastest.