From owner-freebsd-current Tue Aug 17 9:32:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id DC0D31574D for ; Tue, 17 Aug 1999 09:32:47 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA12862; Tue, 17 Aug 1999 09:31:50 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA01918; Tue, 17 Aug 1999 09:31:48 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 17 Aug 1999 09:31:48 -0700 (PDT) Message-Id: <199908171631.JAA01918@vashon.polstra.com> To: randy@psg.com Subject: Re: make cvsup broken In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Randy Bush wrote: > ===> client > m3build > mkdir FreeBSD2 > --- building in FreeBSD2 --- > "/usr/ports/net/cvsup/work/cvsup-16.0/client/src/m3makefile", line 1: unable to read ".M3EXPORTS" > from directory "FreeBSD2" of package "formsvbt" (/usr/local/lib/m3/pkg/formsvbt) I don't believe the port is broken. Nobody has changed it recently. Maybe your disk filled up. Maybe you ran out of memory. Make sure you have plenty of swap, and use "ulimit" or "limit" to remove any memory-related resource limits prior to building the port. From the weird stuff in your other recent bug reports, I also think it's entirely possible that your hardware or kernel or filesystems are messed up. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message