portupgrade anything causes infinite fork loop
mar...@marcuscom.com
"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.
Joe
--
PGP Key: http://www.marcuscom.com/pgp.asc
To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
fl...@energyhq.homeip.net
--98e8jtXdkpgskNou
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, May 10, 2002 at 01:00:44PM -0400, Joe Marcus Clarke wrote:
Hi,
> cause this. I checked CVS for the recent ports infrastructure changes,
> but I don't think that's causing the problem.
>=20
> I'm simply running portupgrade gettext, but all ports fail in the same
> manner.
>=20
> 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.
Cheers,
--=20
Miguel Mendez - fl...@energyhq.homeip.net
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
FreeBSD - The power to serve!
--98e8jtXdkpgskNou
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)
iD8DBQE82/8anLctrNyFFPERAinXAJ4qxdWKFrCtwL9aSMeiAo+YCI9UWQCgq/Ai
GqqRmYCrrolqoUHU84ZEezs=
=sUs+
-----END PGP SIGNATURE-----
--98e8jtXdkpgskNou--
sob...@freebsd.org
>
> 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
sob...@freebsd.org
>
> 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:
> > > 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.
> >
> >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.
>
> 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.
Should be resolved now (textproc/expat2/Makefile rev.1.14). Sorry for
confusion and thanks to all who reported!
ne...@nevermind.kiev.ua
On Fri, May 10, 2002 at 08:45:08PM +0300, you wrote:
> > 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.
>
> Should be resolved now (textproc/expat2/Makefile rev.1.14). Sorry for
> confusion and thanks to all who reported!
Thanx, it works.
--
NEVE-RIPE