On Tue, Jul 16, 2013 at 6:28 PM, Paul Eggleton < paul.eggle...@linux.intel.com> wrote:
> I just got around to trying this again, only this time I cloned a new poky > tree in a different path which should replicate your situation and used > SSTATE_MIRRORS to point to the previous sstate-cache. It built completely > from > sstate as it expected. For reference I was testing with the latest dylan > branch and core-image-minimal. > > As I said earlier, if you look at the code only the checksum value goes > into > the task checksum and not the filename, so the path to the base of the > metadata > changing cannot influence the task checksum. However, I think I can see > how you > would think that the paths changing influenced the checksum, since the data > that we put into the siginfo file *does* contain the full path, and thus > bitbake-diffsigs will report that as having changed even though that > difference > didn't change the task checksum. That is a bug and we should fix how we > store > paths either in the cache or in the siginfo file, but that fix will have > to take > into account different layer paths. I'd suggest a simpler and more reliable > approach would be to just get the relative path to os.path.dirname of the > recipe rather than TOPDIR. > > As far as I can tell though that won't actually fix the issue triggering > rebuilds in your case. Something else must be changing. It would be > interesting if you could dig into what that might be as I can't reproduce > the > rebuilding issue here. > on a related topic, we have given a 'hands on workshop' last week at our Linaro Conference. in order to avoid potential network issues and wasting too much time building, we had prepared 'tarballs' for 1) download folder, 2) sstate For sstate we have prepared a couple of such archive for OpenSuse and Ubuntu (12.04, 13.04) for both 32-bit and 64-bit variants. We used 'dylan' in our workshop since the archives were created a couple of days before, to avoid new commits in master. Interesting remarks: - 'download' archive worked nicely for everyone - 'sstate' archive worked for some people, but not everyone. In my particular case I was able to run a complete build from sstate without rebuilding *anything* using the 13.04-64 sstate tarball. but for some people it only used the sstate partially. I didn't get a chance to 'debug' what the problem was. but all our files are available in case some more folks want to play with them. You can download the archives here: http://people.linaro.org/~trevor.woerner/LCE2013/ And the instructions to recreate the 'build env' (e.g. checkout the layers) is described here: https://collaborate.linaro.org/x/NYBm
_______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
