From owner-freebsd-current Fri Oct 29 12:23:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id EB64C15575 for ; Fri, 29 Oct 1999 12:23:18 -0700 (PDT) (envelope-from street@iname.com) Received: from mired.eh.local ([24.64.136.188]) by mail.rdc2.on.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991029192317.TSGS3040.mail.rdc2.on.home.com@mired.eh.local>; Fri, 29 Oct 1999 12:23:17 -0700 Received: (from kws@localhost) by mired.eh.local (8.9.3/8.9.3) id PAA22063; Fri, 29 Oct 1999 15:23:17 -0400 (EDT) (envelope-from kws) To: "Russell L. Carter" Cc: brdean@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: emacs / ncurses - problem somewhere References: <199910291808.LAA07310@vip.consys.com> From: Kevin Street Date: 29 Oct 1999 15:23:17 -0400 In-Reply-To: "Russell L. Carter"'s message of "Fri, 29 Oct 1999 11:08:32 -0700 (MST)" Message-ID: <87904mq8d6.fsf@mired.eh.local> Lines: 14 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Biscayne" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Russell L. Carter" writes: > Yup! And also for 19.34b... I've searched all over for the > source of this problem, glad to know I'm not alone. However, > it only affects one of my three -current boxes, so apparently there is > bit of cruft lying around, but I haven't been able to find > the sucker causing this. (mergemaster'd repeatedly) Are the ones that work linked with an old version of libtermcap.so that was lying around or are they linked with the new libncurses.so.5 ? -- Kevin Street street@iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message