Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 May 2002 13:19:01 -0400
From:      Garance A Drosihn <drosih@rpi.edu>
To:        Miguel Mendez <flynn@energyhq.homeip.net>, Joe Marcus Clarke <marcus@marcuscom.com>
Cc:        ports@FreeBSD.ORG, knu@FreeBSD.ORG
Subject:   Re: portupgrade anything causes infinite fork loop
Message-ID:  <p0511175db901b0c86596@[128.113.24.47]>
In-Reply-To: <20020510191050.B66230@energyhq.homeip.net>
References:  <1021050045.320.57.camel@gyros.marcuscom.com> <20020510191050.B66230@energyhq.homeip.net>

next in thread | previous in thread | raw e-mail | index | archive | help
At 7:10 PM +0200 5/10/02, Miguel Mendez wrote:
>
>On Fri, May 10, 2002 at 01:00:44PM -0400, Joe Marcus Clarke wrote:
>  > 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.
>
>Ricardo Torrini has reported a similar problem in another list.
>It seems to be related to the 'make clean' call, that causes
>an infinite loop.  IIRC portupgrade make cleans ports before
>building them. It seems to me it's not portupgrade's fault.

Note that Richard is not even using portupgrade, he is just
doing a 'make clean' in the directory for the 'gettext' port.
His problem is *definitely* not portupgrade, and the problem
you describe is probably the same as the problem he reported.

-- 
Garance Alistair Drosehn            =   gad@gilead.netel.rpi.edu
Senior Systems Programmer           or  gad@freebsd.org
Rensselaer Polytechnic Institute    or  drosih@rpi.edu

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0511175db901b0c86596>