From owner-freebsd-current  Sun Oct 25 07:55:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA22914
          for freebsd-current-outgoing; Sun, 25 Oct 1998 07:55:41 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22909
          for <freebsd-current@FreeBSD.ORG>; Sun, 25 Oct 1998 07:55:38 -0800 (PST)
          (envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
	by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA23021;
	Sun, 25 Oct 1998 10:55:03 -0500 (EST)
Date: Sun, 25 Oct 1998 10:55:02 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: Nathan Dorfman <nathan@rtfm.net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: libmytinfo breaks vim-5.3 port, maybe others?
In-Reply-To: <19981023205115.A5357@rtfm.net>
Message-ID: <Pine.BSF.4.05.9810251053440.22868-100000@zone.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hmm... I never bothered checking that. I noticed that tputs broke it, so I
commented out that define (HAVE_TERMWHATEVER) in that single file with
tputs. But pleased to know someone figured out what was really going on,
even if it doesn't matter much to me since changing that tputs works as
well :)

Cheers,
Brian Feldman

On Fri, 23 Oct 1998, Nathan Dorfman wrote:

> Vim-5.3 (compiled from ports) won't run in -g (gvim) mode with
> libmytinfo. At first I thought it was vim breakage, or Motif/Athena
> or even X11 breakage. But read on:
> 
> CPU states: 14.8% user,  0.0% nice, 84.0% system,  1.2% interrupt,  0.0% idle
> 
>  5411 root      89   0  3692K  2960K RUN      0:33 92.19% 76.98% vim
>   243 nathan     2   0 12344K  4060K select  21:49  4.39%  4.39% XF86_SVGA
> 
> After gdb vim 5411, it has this to say:
> 
> (gdb) bt
> #0  0x283524da in tputs ()
> #1  0x80a7146 in XtVaGetApplicationResources ()
> #2  0x807bb81 in XtVaGetApplicationResources ()
> #3  0x808c865 in XtVaGetApplicationResources ()
> #4  <signal handler called>
> #5  0x283524da in tputs ()
> #6  0x80a7146 in XtVaGetApplicationResources ()
> #7  0x80a7ab9 in XtVaGetApplicationResources ()
> #8  0x806f84d in XtVaGetApplicationResources ()
> #9  0x804b275 in XtVaGetApplicationResources ()
> 
> Anyway, I noticed something weird:
> 
>         libmytinfo.so.2 => /usr/lib/libmytinfo.so.2 (0x2834b000)
> 
> According to find -exec grep, this library is not mentioned anywhere
> in the vim port or work dir. Are things being linked with it automagically
> for some reason? Anyway, moving libtmyinfo.so.2 to foo and rebuilding
> vim: built and ran fine. Anyone? Pilot error?
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 


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