From owner-freebsd-current@FreeBSD.ORG Sun Jul 20 18:44:47 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DF9037B401 for ; Sun, 20 Jul 2003 18:44:47 -0700 (PDT) Received: from schnell.net (schnell.net [209.50.225.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1096143FAF for ; Sun, 20 Jul 2003 18:44:46 -0700 (PDT) (envelope-from loschert@servint.com) Received: from schnell.net (localhost [127.0.0.1]) by schnell.net (8.12.8p1/8.12.8) with ESMTP id h6L1ihgc047620; Sun, 20 Jul 2003 21:44:43 -0400 (EDT) (envelope-from loschert@servint.com) Received: from localhost (matt@localhost) by schnell.net (8.12.8p1/8.12.8/Submit) with ESMTP id h6L1ihgw047617; Sun, 20 Jul 2003 21:44:43 -0400 (EDT) (envelope-from loschert@servint.com) X-Authentication-Warning: schnell.net: matt owned process doing -bs Date: Sun, 20 Jul 2003 21:44:43 -0400 (EDT) From: Matt Loschert X-X-Sender: matt@schnell.net To: Tim Kientzle In-Reply-To: <3F183EF9.7020506@acm.org> Message-ID: <20030720214202.S47601@schnell.net> References: <20030715100839.F41961@inton.Ninja-assassin.com> <20030716133802.K18278@schnell.net> <20030716181354.GA44980@dan.emsphone.com> <20030717074756.B17029@gamplex.bde.org> <20030717123524.T24327@schnell.net> <20030718154832.K21942@gamplex.bde.org> <20030718095946.H29869@schnell.net> <3F183EF9.7020506@acm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Buildworld fails in 5.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 01:44:47 -0000 On Fri, 18 Jul 2003, Tim Kientzle wrote: > Matt Loschert wrote: > > After grepping through the build log > > for error messages, I found the following output, which appears to be some > > sort of build loop gone wild: > > > > First this > > ---------- > > Results of making rescue.cache: > > MAKEOBJDIRPREFIX=/usr/obj/usr/src/rescue/rescue crunchgen -q -m rescue.mk -c rescue.c rescue.conf > > > > > > Then the following output repeated 363 times > > -------------------------------------------- > > > > crunchgen: make error: Remaking `crunchgen_objs' > > > > crunchgen: make error: Results of making crunchgen_objs: > > > > crunchgen: make error: > > > > crunchgen: make error: Remaking `loop' > > > > crunchgen: make error: Results of making loop: > > > > crunchgen: make error: > > > > > > With the following output repeated 2 times within the above output > > ------------------------------------------------------------------ > > > > Run "make -f rescue.mk" to build crunched binary. > > *** Error code 1 > > Results of making rescue.mk: > > MAKEOBJDIRPREFIX=/usr/obj/usr/src/rescue/rescue crunchgen -q -m rescue.mk -c rescue.c rescue.conf > > > > > > I suppose this means that there is a dependency missing for the rescue > > crunchgen target? > > Good work, Matt. > > I wrote the /rescue stuff and a lot of people have > reported that it breaks parallel builds, but I haven't yet > come up with anything. (In part, because I haven't yet > managed to reproduce it. ) > > A couple of things look odd about this: > > 1) You should not be building 'rescue.mk' twice. > That could be the problem right there, if the rescue.mk > makefile is getting rebuilt (overwritten) while another > build thread is using it. The dependencies in > rescue/rescue/Makefile look right to me, but I > could be missing something. > > 2) I can't find the 'crunchgen_objs' or 'loop' > targets offhand. I'm doing a more extensive > find/grep search right now to see if I can figure > out where those are coming from. > > Somewhere in here is the answer to this problem, > I just don't see it yet. > > Tim Kientzle > > P.S. Could you email me the log from your build > that failed? Sure. I have it on one of my machines at work. I will email it to you on Monday morning.. > Could you try a lower -j value? If -j 2 fails, > for instance, that might be easier to diagnose. > Thanks for all your help. Definitely, I will fire off a build when I get in on Monday. Thanks, - Matt -- Matt Loschert - Software Engineer | email: loschert@servint.com | ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA | phone: (703) 847-1381 |