From owner-freebsd-current  Fri Oct 29 13:25:56 1999
Delivered-To: freebsd-current@freebsd.org
Received: from vip.consys.com (VIP.ConSys.COM [209.141.107.6])
	by hub.freebsd.org (Postfix) with ESMTP id ACA3215546
	for <freebsd-current@freebsd.org>; Fri, 29 Oct 1999 13:25:51 -0700 (PDT)
	(envelope-from rcarter@pinyon.org)
Received: (from pinyon@localhost)
	by vip.consys.com (8.9.3/8.9.1) id NAA07594
	for freebsd-current@freebsd.org; Fri, 29 Oct 1999 13:25:47 -0700 (MST)
Date: Fri, 29 Oct 1999 13:25:47 -0700 (MST)
From: "Russell L. Carter" <rcarter@pinyon.org>
Message-Id: <199910292025.NAA07594@vip.consys.com>
To: freebsd-current@freebsd.org
Subject: Re: emacs / ncurses - problem somewhere
In-Reply-To: <87904mq8d6.fsf@mired.eh.local>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

|"Russell L. Carter" <rcarter@pinyon.org> 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 ?

ldd emacs on -current with the bug:

        libncurses.so.5 => /usr/lib/libncurses.so.5 (0x2824a000)

ldd emacs on -current without the bug (different system):

        libtermcap.so.2 => /usr/lib/libtermcap.so.2 (0x1828c000)

Russell

|
|-- 
|Kevin Street
|street@iname.com
|


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message