I can verify that these steps worked for me also. When I tried earlier, I forgot to turn off the screen lock.
- Jon ----- Original Message ----- > Here's what I did: > > - flash 122 base image > - enable adb > - disable screen lock (prevents adb from being disabled when the screen turns > off) > - rm -rf backup-flame and out/target/product/flame/firmware.hash > - rebuild and it should pull a new backup-flame directory > > Dave Hylands > > ----- Original Message ----- > > > From: "Jonathan Hylands" <[email protected]> > > To: [email protected] > > Sent: Monday, July 14, 2014 9:12:16 AM > > Subject: Re: [b2g] If your flame build fails because of missing > > time_daemon, > > read this! > > > I was getting this error this morning, so I tried to do this, and now I'm > > getting a different file error: > > > Pulling "chrome.manifest" > > cp: cannot stat > > ‘../../../backup-flame/system/b2g/distribution/bundles/b2g_time/chrome.manifest’: > > No such file or directory > > Failed to pull chrome.manifest. Giving up. > > > I used the build in > > https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/tinderbox-builds/b2g-inbound-flame-eng/latest/ > > > and flashed my flame with that, and then attempted to rebuild using latest > > master (after deleting my backup-flame directory). > > > I got this in the build log: > > > 1587 files pulled. 0 files skipped. > > 1569 KB/s (321551578 bytes in 200.026s) > > > so it appears all the files it is supposed to get are there. > > > Any ideas? > > > Thanks, > > Jon > > > ----- Original Message ----- > > > PSA: Bug 1032233 landed recently which tries to pull a time_daemon > > > binary into the backup-flame directory. If you've been doing local > > > builds for flame, your device may not have this file, and your build > > > will fail. This is the same problem as the missing libgps.utils.so that > > > happened earlier, and the steps to fix are the same (see below). > > > > > > Cheers, > > > kats > > > > > > On 16/5/2014, 9:20, Kartikaya Gupta wrote: > > > > My flame build, which was working yesterday, broke this morning. See > > > > bug > > > > 1011481 for details, but here's the quick solution (note that this will > > > > completely erase everything on your device): > > > > > > > > - Download the latest flame.zip from the b2g-inbound pvtbuild folder > > > > [1] > > > > - Unpack it and run the ./flash.sh script inside the b2g-distro folder > > > > - Delete your backup-flame directory > > > > - Rebuild as usual > > > > > > > > The reason this happened is that some extra libraries were added to the > > > > flame build, and devices that were flashed from old pvtbuilds won't > > > > have > > > > these libraries. Therefore, if you have a backup-flame dir from prior > > > > to > > > > this change, it won't have these libraries either, and your build will > > > > fail. > > > > > > > > The new libraries were added yesterday and haven't made it into the > > > > latest mozilla-central pvtbuild yet, but they have made it into the > > > > latest b2g-inbound pvtbuild, so flashing that and rebuilding your > > > > backup-flame dir fixes it. > > > > > > > > From what Alex Lissy said I believe this might happen a few more times > > > > in the future as additional libraries are added to the flame build, so > > > > if you do get build errors in the future following these steps should > > > > fix it for you. > > > > > > > > Cheers, > > > > kats > > > > > > > > [1] > > > > https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/tinderbox-builds/b2g-inbound-flame-eng/latest/ > > > > > > > > > > _______________________________________________ > > > dev-b2g mailing list > > > [email protected] > > > https://lists.mozilla.org/listinfo/dev-b2g > > > > > _______________________________________________ > > dev-b2g mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
