Date: Tue, 21 Nov 2000 00:38:15 -0800 From: Kent Stewart <kstewart@urx.com> To: Don Lewis <Don.Lewis@tsc.tdk.com> Cc: Sheldon Hearn <sheldonh@uunet.co.za>, Marcel Moolenaar <marcel@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src Makefile.inc1 src/gnu/usr.bin/perl Makefile Makefile.inc src/gnu/usr.bin/perl/library Makefile.inc src/gnu/usr.bin/perl/miniperl Makefile src/gnu/usr.bin/perl/pod Makefile.inc src/gnu/usr.bin/perl/utils Makefile.inc ... Message-ID: <3A1A3477.F672FFA0@urx.com> References: <18475.974709241@axl.fw.uunet.co.za> <3A18E903.C1E97D46@urx.com> <200011210753.XAA27368@salsa.gv.tsc.tdk.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Don Lewis wrote: > > On Nov 20, 1:04am, Kent Stewart wrote: > } Subject: Re: cvs commit: src Makefile.inc1 src/gnu/usr.bin/perl Makefile M > } > } > } Sheldon Hearn wrote: > } > > } > On Sun, 19 Nov 2000 18:17:35 PST, Marcel Moolenaar wrote: > } > > } > > o Add chmod to the list of saved tools, because perl > } > > conditionally uses it during install. > } > > } > Other tools that have reported to be problematic for x.x -> 4.x-STABLE > } > upgrades are sort and tr. I'm still waiting for the originator of the > } > PR to produce build failure output so that we can verify that they're > } > required. > } > } If you want to see failures, it is easy. All you had to do is go to > } the archive and search on "libsdbm.a" and then, only look at the ones > } dealing with installworld failures. > > I suspect it is either a make bug or a filesystem timestamp bug. I've > only gotten bitten by this once. For some reason it wants to rebuild > libsdbm.a from the .o files at install time, even though the libsdbm.a > was already built once. Because libsdbm.a is so small, it will generally > be only be a bit older that the .o files. > > Alas when the failure occurs, libsdbm.a gets overwritten which destroys > its original timestamp. I've given some thought to tweaking the Makefile > to run chmod both before and after the ar command, so that if the install > tries to rebuild libsdbm.a it will fail (because chmod is missing) before > the timestamp can be updated. I figured that it was a buildworld make problem and the installworld problem is just a symptom of the prior failure. It just so happens that adding chmod to the installworld "prog's" will take care of the symptom. There are numerous samples of chmod being needed; however, I think you need to see the output from the buildworld that made it fail. I've had it occur on two of my machines but never when I was capturing the buildworld output. I capture the entire upgrade sequence now and figured sooner or later I would see the chmod happen on the install. I've also gone to a DSL Internet connection and my times are tracking a NTP server pretty well. If you can't build Perl5, checking your system time has always seemed to be one of the solutions. I haven't had a libsdbm.a failure since then. A failure from 11/2 went like > ===> gnu/usr.bin/perl/library/SDBM_File > cd /usr/obj/usr/src/gnu/usr.bin/perl/library/SDBM_File/ext/SDBM_File > ; make -B install INSTALLPRIVLIB=/usr/libdata/perl/5.00503 > INSTALLARCHLIB=/usr/libdata/perl/5.00503/mach > cd sdbm && make all > rm -rf libsdbm.a > ar cr libsdbm.a sdbm.o pair.o hash.o && : libsdbm.a > chmod 755 libsdbm.a > chmod:No such file or directory > *** Error code 1 > Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A1A3477.F672FFA0>