On 1/29/07, Martin Costabel <[EMAIL PROTECTED]> wrote: > Is it possible (since we are on 2-processor machines > here) that some thread of "make install" hasn't quite finished when > dpkg-deb is already starting to wrap up?
As another datapoint, I have seen the "file changed as we read it" error on a single-processor G4 laptop. In my experience, "make -j" generally waits for all of its subprocesses to exit before returning (even when failing on an error). The only case where that might not catch everything is if a make target adds an ampersand to put the command in the background - which is probably a Bad Idea(tm) anyway. I haven't run into this much, but if I had time to debug tar, I'd try adding a debug printf that says *what* actually changed (since I suspect it's just metadata, like stat's atime or mtime). -- - Charles Lepple ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
