Re: bisect gives strange answer
- From
Sam Ravnborg <sam@ravnborg.org>
- Date
- Aug 4, 2005, 19:28 UTC
- Message-ID
- <20050804192838.GB26714@mars.ravnborg.org>
- In-Reply-To
- <E1E0jiv-0003c4-00@skye.ra.phy.cam.ac.uk>
Show 6 quoted lines
> > 1. The kernel Makefiles ar do not understand every subtle dependency. > So they might get confused by updating to different tree states (as > the bisect progresses) because those updates change Makefiles and > include files. In other words, I should have done 'make clean' or > 'make mrproper' before each kernel compile.
If you see any sort of evidence that this would hold true I really like to know. The current build system is only known to fail if a changed file gets a timestamp that is not equal to 'now'. Some braindead SCM uses the timestamp of the chekin.
There has been put a tremendous effort in tracking each and every subtle dependeny - and if something is missing then it ought to be fixed.
Sam