Date: 14 Jul 2003 21:59:45 +0100 From: Stacey Roberts <stacey@vickiandstacey.com> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: FreeBSD Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: make index strangeness after today's cvsup of ports tree Message-ID: <1058216384.64468.45.camel@localhost> In-Reply-To: <20030714203606.GA52774@happy-idiot-talk.infracaninophile.co.uk> References: <1058214037.64468.42.camel@localhost> <20030714203606.GA52774@happy-idiot-talk.infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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.., Cheers! Stacey > Etc. ad nauseam. > > Cheers, > > Matthew -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1058216384.64468.45.camel>