From: Jerry Van Baren <vanbaren_gerald@si.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: [Question] I want to use CSCOPE to port Linux kernel.
Date: Thu, 20 Sep 2001 11:27:10 -0400 [thread overview]
Message-ID: <4.3.2.20010920112423.00b71f00@falcon.si.com> (raw)
In-Reply-To: <20010920143200.79354.qmail@web11002.mail.yahoo.com>
You may also want to find a real libncurses.so.4 and install it rather
than symlinking libncurses.so.5 to it. You probably will be able to
get away with the symlink, but changes in major revs (4->5) tend to
indicate significant changes in parts of the interface (API), which
would cause the caller great consternation if it was unlucky and called
a function whose interface had changed.
gvb
At 07:32 AM 9/20/01 -0700, Dan Bethe wrote:
> > I have already libncurses.so.5.2
> >
> > So I tried as below, but I had the same result.
> > ---------------------------------------------------
> > # ln -s libncurses.so.5.2 libncurses.so.4
> > # rpm -ivh cscope-15.3-1.i386.rpm
> > error: failed dependencies:
> > libncurses.so.4 is needed by cscope-15.3-1
>
> Hi there. RPM's dependancies are based on its database, and
> not on the actual
>filesystem. So the 'ln' wouldn't make any difference in this
>case. Try this:
>
># rpm -ivh --nodeps cscope-15.3-1.i386.rpm
>
> That bypasses RPM's opinion of what is and should be
> installed, so you might
>always have to remember that as a one-off.
>
>=====
>Medium System Administrator and Junior I.T. Manager of 5 yrs
> -- Now available -- Linux, MacOS, Unix-like systems
> -- http://mmmgood.net -- dan_bethe@yahoo.com
>
>
******************** Lawyer gibberish: ********************
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-09-20 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 11:08 [Question] I want to use CSCOPE to port Linux kernel THEDREAM
2001-09-20 14:32 ` Dan Bethe
2001-09-20 15:27 ` Jerry Van Baren [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=4.3.2.20010920112423.00b71f00@falcon.si.com \
--to=vanbaren_gerald@si.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).