Richard Purdie <[email protected]> writes: >> > where the option was added deliberately to deal with time mismatch >> > between autobuilders which was causing real world bugs. >> >> But the real bug is the time mismatch in the autobuilders, isn't it? >> And this can/should be solved by synchronizing time by ntp on them >> instead of applying dirty hacks like resetting file dates. > > I have asked that ntp be installed/fixed on the autobuilders to sort the > problem out but it seems that even with ntp running, mismatches can > happen (e.g. misconfigured timezones).
Really? The only timezone related problems might arise when a package makes 'touch -d <date>' during build. But I can not remember that I have ever seen such a package and this problem should be easy to localize. Else, timezone configuration is completely uninteresting for comparing timestamps or for setting time from ntp. > Worse, when this does happen the failures are extremely unpredictable > and hard to debug. It causes things to repeatedly recompile for example, > even during do_install. How comes do_install() into the game? 'populate-lic' are the only sstate files created before do_install() and I can not imagine how they affect the other build phases; do_compile() results are not sstated (and with the 'tar -m' thing, timestamps get havoc completely causing unpredictable rebuilds). When do_install() is executed, all the following sstate files (populate_sysroot, package) are invalidated and must be recreated. So your problem with do_install() sounds more like an incomplete/racy cleanup of old files. Enrico _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
