On Monday 14 July 2003 01:59 pm, Stacey Roberts wrote:
> Hello Matthew,
>
> On Mon, 2003-07-14 at 21:36, Matthew Seaman wrote:
> > On Mon, Jul 14, 2003 at 09:20:38PM +0100, Stacey Roberts wrote:
> > > Hello,
> > >      After today's cvsup'd ports tree (and portupgrade of gnome-2
> > > to latest in ports), make index returns some weird messages.
> > >
> > > Here is the tail of it:
> > > 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
> > > "Makefile", line 27: warning: Couldn't exec "cd
> > > /devel/libgnugetopt; make -V WRKSRC"
> > > "/usr/ports/Mk/bsd.port.mk", line 1632: warning: Couldn't exec
> > > "id -u" "/usr/ports/Mk/bsd.port.mk", line 1680: warning: Couldn't
> > > exec "/usr/bin/basename /usr/ports/x11/xstroke"
> > > "/usr/ports/Mk/bsd.port.mk", line 1691: warning: Couldn't exec
> > > "/usr/sbin/pkg_info -P 2>/dev/null | /usr/bin/sed -e 's/.*: //'"
> > > "/usr/ports/Mk/bsd.port.mk", line 2379: warning: Couldn't exec
> > > "/bin/cat /var/db/port.mkversion"
> > > Cannot fork: Resource temporarily unavailable
> > > "/usr/ports/Mk/bsd.port.mk", line 1691: warning:
> > > "/usr/sbin/pkg_info -P 2>/dev/null | /usr/bin/sed -e 's/.*: //'"
> > > returned non-zero status Done.
> > > #
> > >
> > > Does anyone know what these messages mean?
> >
> > Someone made an error when committing to ports and consequently
> > 'make index' goes bezerk.  I just noticed that myself.  The
> > offending line appears to be:
> >
> >     GETOPTDIR!=     cd ${PORTSDIR}/devel/libgnugetopt; make -V
> > WRKSRC
> >
> > in the x11/xstroke port.  If you try and run any make command,
> > you'll get a similar effect:
> >
> >     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.

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html

_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to