From owner-freebsd-ports Fri Sep 13 10:48:32 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6428E37B400; Fri, 13 Sep 2002 10:48:27 -0700 (PDT) Received: from creme-brulee.marcuscom.com (rdu57-17-158.nc.rr.com [66.57.17.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id A800743E6E; Fri, 13 Sep 2002 10:48:26 -0700 (PDT) (envelope-from marcus@marcuscom.com) Received: from [10.2.1.2] (vpn-client-2.marcuscom.com [10.2.1.2]) by creme-brulee.marcuscom.com (8.12.5/8.12.5) with ESMTP id g8DHjjiv019587; Fri, 13 Sep 2002 13:45:45 -0400 (EDT) (envelope-from marcus@marcuscom.com) Subject: Re: fork bombs registering packages using GNOMENG From: Joe Marcus Clarke To: alane@geeksrus.net Cc: FreeBSD Ports List , FreeBSD Gnome Team In-Reply-To: <20020913173752.GA53609@wwweasel.geeksrus.net> References: <20020913173752.GA53609@wwweasel.geeksrus.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 13 Sep 2002 13:48:20 -0400 Message-Id: <1031939300.657.31.camel@gyros.marcuscom.com> Mime-Version: 1.0 X-Spam-Status: No, hits=-3.4 required=5.0 tests=IN_REP_TO,DOUBLE_CAPSWORD,AWL version=2.31 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 On Fri, 2002-09-13 at 13:37, Alan E wrote: > I've noticed a distressing trend in ports which use the GNOMENG > configuration interface. If you set USE_GNOME on the make command line, > the port is likely to fork makes until it can't fork anymore - each one > forks a child, which forks a child, which ... up to thousands of them. > > For example, irc/xchat: "make USE_GNOME=gtk12 package" will fork bomb > during the registering package phase of the post-installation code. Why are you doing this? This is wrong. You should never specify USE_* on the make command line. If you're trying to enforce GNOME dependence, use: make -DWITH_GNOME package > > There's something seriously wrong here. I'm using an absolutely > up-to-date ports tree (updated every 2 hours). Does anybody have a clue > as to how this could be happening? > > Personally, I don't think the GNOMENG code was ready for prime time, > and the ports were not updated thoroughtly. Two ports so far, xmms and > sdl12, can't turn off esound support without Makefile modifications. > I'm sure there are others. BTW Max could you please commit the fix to > sdl12? I cc'd you on the pr. Thanks. This has nothing to do with GNOMENG. Apparently xmms was broken even under the old GNOME infrastructure. No where in bsd.gnome.mk does it pass --disable-esound to configure. Since sobomax is the maintainer of sdl12, I think I'll let him do the commit. I agree there were some problems with the switch-over. I'm trying to get those cleaned up. However, I think the problems you're describing are a mix of user error and pre-existing bugs. Joe > > -- > Alan Eldridge > Unix/C(++) IT Pro, 20 yrs, seeking new employment. > (http://wwweasel.geeksrus.net/~alane/resume.txt) > KDE, KDE-FreeBSD Teams (http://www.kde.org, http://freebsd.kde.org/) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-gnome" in the body of the message > -- PGP Key : http://www.marcuscom.com/pgp.asc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message