> > O = OK > > F = Failure(s), extended report at the bottom > > ? = still running or test results not (yet) available > > Build failures during: - = unknown > > c = Configure, m = make, t = make test-prep > > > > 18125 Configuration (common) -Dcc=gcc -Ui_db > > ------- -------------------------------------------------------------- > > O O m m > > F F m m -Dusethreads > > | | | +- PERLIO = perlio -DDEBUGGING > > | | +--- PERLIO = stdio -DDEBUGGING > > | +----- PERLIO = perlio > > +------- PERLIO = stdio > > > > Failures: > > > > dec_osf [stdio/perlio]-Dcc=gcc -Ui_db -Dusethreads > > ext/Time/HiRes/HiRes.................FAILED at test 17 > > .../ext/Time/HiRes/HiRes....FAILED test 17 > > Whose module is that failing there? =|8-PPPPPPPPP > > But, but, but, what's the m's? Have a peek at mktest.log to see why it fails
I would ignore this failure completely-- I was adjusting the scripts while the build was ongoing. -- Jarkko Hietaniemi <[EMAIL PROTECTED]> http://www.iki.fi/jhi/ "There is this special biologist word we use for 'stable'. It is 'dead'." -- Jack Cohen
