On Sun, Jan 23, 2005 at 04:14:28PM +0100, Abe Timmerman wrote: > Op een grimmige winterdag (Sunday 23 January 2005 14:51),schreef Nicholas > Clark: > > On Sun, Jan 23, 2005 at 02:45:53PM +0100, Abe Timmerman wrote: > > > Manual rebuild/rerun: > > > > > > ok 65 > > > # make = 'make' > > > > > > Stop. > > > not ok 66 # make failed: 256 > > > # Makefile out-of-date with respect to Makefile.PL > > > # Cleaning current config before rebuilding Makefile... > > > # make -f Makefile.old clean > /dev/null 2>&1 || /bin/sh -c true > > > # ../../perl "-I../../../lib" "-I../../../lib" Makefile.PL > > > "PERL_CORE=1" # Checking if your kit is complete... > > > # Looks good > > > # Writing Makefile for ExtTest > > > # ==> Your Makefile has been rebuilt. <== > > > # ==> Please rerun the make command. <== > > > # false > > > # *** Error exit code 1 > > > # ext-15332 being removed... > > > FAILED tests 66-272 > > > > > > These are at random places, but always there! > > > > Oooh. I wonder if this is the cause on various platforms. I never see this > > on anything I have access to. > > B > > Could this be timestamp issues with Makefile/Makefile.PL? Is this building > > on a local file system? > > Yup, this is a local filesystem. Perhaps Merijn can shed some light regarding > the type of fs: > > /home on /dev/vg00/lvol5 delaylog,nodatainlog on Sat Sep 25 03:33:08 2004 > > > I'm assuming that MakeMaker is getting caught out > > by timestamps not being what we all expect. > As an aside, I've seen these random failures on OpenBSD as well. Steve Peters steve@fisharerojo.org > Anything I can do to help resolve this? > > Good luck, > > Abe > -- > I'm not denying that it isn't a forest, I'm just leery of what will > fall down if we shake the trees too hard. > -- Jarkko Hietaniemi on p5p @ 2002-02-12Thread Previous | Thread Next