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]>
next in thread | previous in thread | raw e-mail | index | archive | help
--NQTVMVnDVuULnIzU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 ... >=20 > 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. >=20 > For me, 'make buildworld' goes through: > =3D=3D=3D> rescue/rescue/dhcpctl > =3D=3D=3D> rescue/rescue/client > =3D=3D=3D> rescue/rescue/omshell >=20 > successfully, and then while building: > =3D=3D=3D> rescue/rescue/common >=20 > Here is the last few lines I get: >=20 > cc -O -pipe -mcpu=3Dpentiumpro -DIN_GCC -DHAVE_CONFIG_H=20 > -DPREFIX=3D\"/usr\"=20 > -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools=20 > -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools=20 > -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc=20 > -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config=20 > -DHAVE_CONFIG_H -DTARGET_NAME=3D\"i386-undermydesk-freebsd\" -DIN_GCC=20 > -c /usr/src/contrib/gcc/make-temp-file.c > make: don't know how to make=20 > /usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/client/clparse.o.= =20 > Stop > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 >=20 > 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... >=20 > 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. >=20 > 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 --NQTVMVnDVuULnIzU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/EwRzRu2t9DV9ZfsRAjfsAKDBx9ZTdmy+kMj66nhaHjcRco2PEgCgybJL UN+fnkEgB2WxG9tqWiad9jQ= =CyWs -----END PGP SIGNATURE----- --NQTVMVnDVuULnIzU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030714192851.GF12996>