Roland Mainz writes:
> James Carlson wrote:
> > Roland Mainz writes:
> > > - Some dependicies are completely broken for highly-parallel setups
> > 
> > Please file bugs or at least mention what sorts of failures you see.
> > There shouldn't be any broken dependencies in the gate.  If there are,
> > then they're just time bombs waiting for the next high-end build
> > machine to trip over.
> 
> Mhhh... at least in the case of the library dependicies the build will
> not "trip over" (ok, there is a small microscopic gap) if the underlying
> machine has the shared libraries, too. If the *.so* file is missing in
> ${ROOT} then the version from the underlying build machine will be used.

That's even worse, as it means the faults will be unpredictable and
hard to diagnose.

If you see such things, please please do file bugs.

> This is AFAIK only harmfull for builds which add new libraries and add
> broken dependicies but AFAIK it doesn't cause direct harm for the normal
> build (e.g. no exploding puppy heads or build failures).
> The "real fix" (OkOk, not a real fix but it would provide a notification
> mechanism to make sure the dependicies are kept uptodate) may be a
> simple script to check the library dependicies in usr/src/lib/Makefile
> vs. those installed in ${ROOT} (similar to the "nightly" checks which
> run check_rtime).

Yes; something like that is definitely needed.

> > > - Both kernel and userland code could run completely indenepdent
> > 
> > Well thought-out contributions that improve the build process are
> > always welcome.
> 
> Well, AFAIK I posted a patch a whole ago... the problem is that I cannot
> do any testing on my side since the lack any hardware which can exploit
> such a high level of parallism (and somehow I doubt that anyone will
> throw some Niagara machines in my direction (too heavy) or that they
> will magically appear on my desk... ;-( ) ... there is always the gap
> between dreams about "what could be done [with enougth resources]" and
> the reality of having an Ultra5 as main workstation... ;-(

I don't know what patch you're talking about, but I'm asking about
project proposals and/or CR numbers.

-- 
James Carlson, Solaris Networking              <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org

Reply via email to