Date: Mon, 14 Jul 2003 12:28:51 -0700 From: Gordon Tetlow <gordont@gnf.org> To: Garance A Drosihn <drosih@rpi.edu> Cc: current@freebsd.org Subject: Re: Overdone rescue cleaning as part of buildworld? Message-ID: <20030714192851.GF12996@roark.gnf.org> In-Reply-To: <p0521065fbb389c78d5fa@[128.113.24.47]> References: <20030713214715.H15811@root.org> <20030714004042.A38507@hub.freebsd.org> <20030714160952.GD12996@roark.gnf.org> <p0521065fbb389c78d5fa@[128.113.24.47]>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Mon, Jul 14, 2003 at 01:53:29PM -0400, Garance A Drosihn wrote: > At 9:09 AM -0700 7/14/03, Gordon Tetlow wrote: > >On Mon, Jul 14, 2003 at 12:40:42AM -0700, David O'Brien wrote: > > > Gordon, 'make world' times have climbed up to over 1 hour > > > on a machine that used to do it in 25 minutes. Can you > > > please commit to understanding how /resuce is build and > >optimizing it before 5.2-RELEASE. > > > >I've already started this process and I have some work ... > > Btw, when I was doing a buildworld this weekend, I noticed > the following error in the section that builds /rescue. Has > anyone else noticed this? It may be easy to miss, because > 'make buildworld' does not abort at the error. The following > is some information I sent to Tim Kientzle <kientzle@acm.org> > early this morning, but I thought I'd send it to the list just > to see if anyone else has seen this problem. Perhaps it is > due to something at my end of things. > > For me, 'make buildworld' goes through: > ===> rescue/rescue/dhcpctl > ===> rescue/rescue/client > ===> rescue/rescue/omshell > > successfully, and then while building: > ===> rescue/rescue/common > > Here is the last few lines I get: > > cc -O -pipe -mcpu=pentiumpro -DIN_GCC -DHAVE_CONFIG_H > -DPREFIX=\"/usr\" > -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools > -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools > -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc > -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config > -DHAVE_CONFIG_H -DTARGET_NAME=\"i386-undermydesk-freebsd\" -DIN_GCC > -c /usr/src/contrib/gcc/make-temp-file.c > make: don't know how to make > /usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/client/clparse.o. > Stop > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > > Now, after those Error's, make seems to go merrily along, and > makes bunch of other stuff. It looks like it even gets to the > end of the buildworld OK. However the way I do buildworld's > notices those '*** Error' lines, and it starts waving flags at > me. I am generally reluctant to ignore those flags... > > I did a bunch of cvsup's and cross-checks to make sure I had > the correct up-to-the-minute sources. I had also removed > all of /usr/obj/usr/src in case I had old cruft there (well, > actually I did that just because of the new gcc import...). > I rebuilt with -DNORESCUE and the buildworld finished OK. > > I am building with -j5 on a dual-processor Athlon system, if > that is significant. I am not doing any cross-build. I've heard some reports of this specifically with -j flag. I'll see if I can look at it once I finish depessimizing the build. -gordon [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/EwRzRu2t9DV9ZfsRAjfsAKDBx9ZTdmy+kMj66nhaHjcRco2PEgCgybJL UN+fnkEgB2WxG9tqWiad9jQ= =CyWs -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030714192851.GF12996>