From owner-freebsd-current@FreeBSD.ORG Sat Dec 13 10:04:05 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C037A16A4CE for ; Sat, 13 Dec 2003 10:04:05 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDDF643D33 for ; Sat, 13 Dec 2003 10:04:04 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) hBDI445x002068; Sat, 13 Dec 2003 10:04:04 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)hBDI44kV002067; Sat, 13 Dec 2003 10:04:04 -0800 (PST) (envelope-from sgk) Date: Sat, 13 Dec 2003 10:04:04 -0800 From: Steve Kargl To: Cy Schubert Message-ID: <20031213180404.GA2040@troutmask.apl.washington.edu> References: <200312131429.hBDETsqo033570@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200312131429.hBDETsqo033570@cwsys.cwsent.com> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: tcsh in malloc(): error: recursive call X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2003 18:04:05 -0000 On Sat, Dec 13, 2003 at 06:29:54AM -0800, Cy Schubert wrote: > > Making: ../unxfbsd.pro/obj/cfg_yy.obj > cc -w -c -I. -I. -I../inc -I../inc -I../unx/inc -I../unxfbsd.pro/inc -I. > -I/exc > if ( -e ../unxfbsd.pro/obj/cfg_yy.o) touch ../unxfbsd.pro/obj/cfg_yy.obj > tcsh in malloc(): error: recursive call > dmake: Error code 134, while making '../unxfbsd.pro/misc/o_cfg_yy.dpcc' > dmake: '../unxfbsd.pro/misc/o_cfg_yy.dpcc' removed. > ---* TG_SLO.MK *--- > > Stop in /export/local-ports/cvs-ports/ports/editors/openoffice-1.1. > cwsys# > > Some of the discussion I've seen points to the possibility that static > linking may fix this. Should I try linking a static tcsh (or use the one in > /rescue) to test this theory out? Or, is there some other fix or > circumvention to this problem? > What were your CFLAGS and COPTFLAGS when you last updated the base OS? -- Steve