public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Dugger <n0ano@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Can't find libncurses.so.4 in ia32
Date: Fri, 19 May 2000 00:17:32 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205099@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205098@msgid-missing>

Vadim-

This appears to be some issue with version 4 versus version 5 that
I don't understand how `ldconfig' deals with it.  You can get around
the problem by setting `LD_LIBRARY_PATH=/usr/ia32/usr/lib' when
running the IA32 version of `telnet'.  That's what I did and it
worked fine.

On Thu, May 18, 2000 at 04:09:42PM -0700, Vadim Furman wrote:
> Hi,
> When I try to run an ia32 "telnet" , I get an error "Can't find shared
> library libncurses.so.4".
> The libncurses.so.4 library is there in my /usr/ia32/usr/lib directory,
> together with other versions of the ncurses libraries.
> But for some reasons ldconfig doesn't put it in the ld.so.cache, so when I
> do "ldconfig -p | grep ncurses" I see only libncurses.so.5 .
> I am using freshly installed TurboLinux Alpha 2000-05-05, my
> /etc/ld.so.config has /lib,/usr/lib, /usr/X11R6/lib, and
> /usr/ia32/lib,/usr/ia32/usr/lib,/usr/ia32/X11R6/lib
> 
> 
> Vadim Furman           Mainsoft Corporation
> vadimf@mainsoft.com    Phone: (408)544-1430
> Fax: (408)544-1444
> 3850 N. First St.
> San Jose CA. 95134-1702
> 
> 
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64

-- 
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@valinux.com
Ph: 303/938-9838



      reply	other threads:[~2000-05-19  0:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-18 23:09 [Linux-ia64] Can't find libncurses.so.4 in ia32 Vadim Furman
2000-05-19  0:17 ` Don Dugger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590678205099@msgid-missing \
    --to=n0ano@valinux.com \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox