On Tue, 22 Feb 2005, Norman Gray wrote:
> > However, for any fixed set of dependencies expressed in a series of
> > component.xml files, using the same logic (==autobuild?) you would
> > expect
> > the same outcome, wouldn't you. We're clearly not seeing this.
>
> I wasn't sure if we were or not. Since we don't know exactly when the
> nightly-builds run or the repository is rsync'd -- they're not at a
> particular time, nor is the start time written in the build log -- it
> could be that we're seeing platform-specific behaviour only because
> different platforms happen to have slightly different dependencies in
> the generated Makefile.in.
I'd say this wasn't the case, simply because the problems persist for days
at a time, surely they must synchronize at some point.
> Alternatively, and possibly more plausibly, since the transformation
> from dependencies to build order is done by make, the make
> implementations on Tru64 (bsdmake?) and Debian might simply be
> producing a different build order from the make (GNUmake) on RH and OS
> X.
If indeed make is still involved. Only Steve can enlighten us about this.
> > The simplest way to check all dependencies for all time would be to use
> > the Makefile system to cold-build each component from its manifest
> > dependencies (which I admit would probably take a week on some of the
> > machines!). When things go wrong that's how I check it (if a quick peer
> > doesn't do it).
>
> That's true, but it probably would take a week! We must be pretty
> close to a correct set of dependencies, now, and the rate of change of
> dependencies edits is slowing down.
We've been saying that for a while now.
Peter.
|