Hi! ----
[CC:'ing mike.sullivan at sun.com (SFWNV gatekeeper) since the issue below is a very general problem in SFWNV...] Danek Duvall wrote: [snip] > I haven't tried to track these down yet, mostly because they've only shown > up on one nightly run so far. That run was characterized by my having > allowed $HOME through in the environment passed to nightly, as well as > jacking up DMAKE_MAX_JOBS from 4 to 20. It smells of a configure run gone > wrong, but why only the once, I don't know. Perhaps something load > related, as 6859442 and 6859444 might be. One thing which needs IMO be discontinued is the attempt to run multiple "configure" runs in parallel. Some of the autoconf stuff has timing-related tests and that causes problems if the build machine is heavily loaded and many of the "configure" scripts use non-unique temporary file names (which is more or less a receipe for getting "random" results). AFAIK these two issues need to be fixed like this: 1. We need a seperate "install_configure" target which is running _serially_ over the tree and then does the "make" calls in normal parallel fashion. 2. Each build needs an own directory for temporary files and set TMPDIR to point to it (and we have to pray that the autoconf stuff honors at least that variable) That would AFAIK eliminate _most_ of the random build failures and miscompiles in SFWNV... ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;)
