From owner-freebsd-ports Fri May 10 10:12:21 2002 Delivered-To: freebsd-ports@freebsd.org Received: from sdns.kv.ukrtel.net (sdns.kv.ukrtel.net [195.5.27.246]) by hub.freebsd.org (Postfix) with ESMTP id EA7A037B400; Fri, 10 May 2002 10:12:15 -0700 (PDT) Received: from vega.vega.com (195.5.51.243 [195.5.51.243]) by sdns.kv.ukrtel.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id J9KHZK3Z; Fri, 10 May 2002 20:14:00 +0300 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g4AHCQ156422; Fri, 10 May 2002 20:12:26 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3CDC0003.A2BA34B9@FreeBSD.org> Date: Fri, 10 May 2002 20:14:43 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Joe Marcus Clarke Cc: ports@FreeBSD.ORG, knu@FreeBSD.ORG Subject: Re: portupgrade anything causes infinite fork loop References: <1021050045.320.57.camel@gyros.marcuscom.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Joe Marcus Clarke wrote: > > I know that I won't figure this out until the second after I press > "Send," so I might as well start the email ;-). > > I have been using portupgrade fine forever up until today. I have a > laptop running 4.6-PRE from yesterday with the latest portupgrade. > Today I cvsup'd my ports and went to do a portupgrade of gettext, as > soon as I did that, portupgrade hung at > > ---> Upgrading 'gettext-0.11.1_2' to 'gettext-0.11.1_3' (devel/gettext) > ---> Building '/usr/ports/devel/gettext' > > After a while, I received a "resource unavailable: fork()" message, and > my load average was over 700 (I've never seen a load average that > high). This happens for anything I try to portupgrade. What I did to > try and fix this is reinstall portupgrade, start with a fresh > pkgtools.conf, and reinitialized my pkgdb.db. Nothing worked. > > I can build new ports just fine using the old make install. I ran > portupgrade with -v, but it wasn't very insightful. > > As far as I know, nothing changed between yesterday and today that would > cause this. I checked CVS for the recent ports infrastructure changes, > but I don't think that's causing the problem. > > I'm simply running portupgrade gettext, but all ports fail in the same > manner. > > Any ideas? Thanks. Bah, that's because gettext now requires expat, expat requires gmake, gmake requires gettext, gettext requires expat, expat requires gmake and so on up to infinity. I'll think how we could resolve that dead loop. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message