Date: Tue, 15 Jul 2003 10:10:54 -0700 From: Kent Stewart <kstewart@owt.com> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: stacey@vickiandstacey.com Subject: Re: make index strangeness after today's cvsup of ports tree Message-ID: <200307151010.54216.kstewart@owt.com> In-Reply-To: <20030715075903.GA67317@happy-idiot-talk.infracaninophile.co.uk> References: <1058214037.64468.42.camel@localhost> <200307141851.51436.kstewart@owt.com> <20030715075903.GA67317@happy-idiot-talk.infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 15 July 2003 12:59 am, Matthew Seaman wrote: > On Mon, Jul 14, 2003 at 06:51:51PM -0700, Kent Stewart wrote: > > On Monday 14 July 2003 01:59 pm, Stacey Roberts wrote: > > > On Mon, 2003-07-14 at 21:36, Matthew Seaman wrote: > > > > happy-idiot-talk:...ports/x11/xstroke:% make -V PORTSDIR > > > > cd: can't cd to /devel/libgnugetopt > > > > cd: can't cd to /devel/libgnugetopt > > > > cd: can't cd to /devel/libgnugetopt > > > > cd: can't cd to /devel/libgnugetopt > > > > cd: can't cd to /devel/libgnugetopt > > > > cd: can't cd to /devel/libgnugetopt > > > > cd: can't cd to /devel/libgnugetopt > > > > cd: can't cd to /devel/libgnugetopt > > > > cd: can't cd to /devel/libgnugetopt > > > > cd: can't cd to /devel/libgnugetopt > > > > cd: can't cd to /devel/libgnugetopt > > > > cd: can't cd to /devel/libgnugetopt > > > > cd: can't cd to /devel/libgnugetopt > > > > cd: can't cd to /devel/libgnugetopt > > > > ... > > > > > > Thanks for that explanation.., I imagine this is another one of > > > those things that eventually sorts itself out.., > > > > The other thing that is happening is the following.from a dmesg > > > > maxproc limit exceeded by uid 0, please see tuning(7) and > > login.conf(5). maxproc limit exceeded by uid 0, please see > > tuning(7) and login.conf(5). maxproc limit exceeded by uid 0, > > please see tuning(7) and login.conf(5). > > > > You get 3 or 4 of these while all of the above is going on. > > Yes. make(1) is invoking itself recursively because of this bug. > The aposite term is "fork bomb". Eventually you'll run out of system > resources and the command will fail. When Stacey said "sorts itself > out", I believe he was talking about getting fixes committed to the > ports tree. He didn't mean that there would be loads of error > messages printed out, and then the command would succeed anyhow. > The are a number of problems with building an INDEX[-5] at this point. The bitch message from Bento seems to be turned off at this moment. With out its constant reminder, things don't seem to get sorted out as fast :). The "make index" runs with your latest patch but a "make index" on a 5-current systems shows some of the problems that exist with /usr/ports/print and the epson printers. On a 4-stable system, you don't see the message but you can view an INDEX and the entry for pips2200 and the entries for a number of nearby ports looks strange. On a 5-current system, there are many other messages for other ports. These just stand out above the rest. One side effect, it caused me to deal with my local mirror. I had it on a small HD and had never got around to adding the last 256MB of memory. Everything was on the system that I was using to do my builds on. Doing builds from KDE on the machine with the mirror was causing a little bit of swaping. Moving the mirror to a different system left a lot more machine available for portupgrade's tools to do their thing while the port structure was being updated on the other systems. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200307151010.54216.kstewart>