> In that case the ldconfig way described by Arindam should have worked.
> Try running ldconfig in verbose mode( with -v option) and see if the
> libc++ library is displayed:
> ldconfig -v | grep sigc
did this, here's the output:
# ldconfig -v | grep sigc
libsigc-1.2.so.5 -> libsigc-1.2.so.5.0.5
libsigc-1.2.so.5 -> libsigc-1.2.so.5.0.5
>
> Also show us:
> 1. The exact RPM message which said libsigc++ was needed.
# rpm -ivh k3d-0.2.5.4-1.i386.rpm
error: Failed dependencies:
libsigc++ >= 1.2 is needed by k3d-0.2.5.4-1
> 2. The list of files which has been installed in /usr/local/lib when you
> did "make install" while building libsigc++.
>
this is under /usr/local/lib
libsigc-1.2.a
libsigc-1.2.la
libsigc-1.2.so
libsigc-1.2.so.5
libsigc-1.2.so.5.0.5
btw, i noticed something rather unusual, and tell me if this has
something to do with the problem:
i discovered a directory called /user/
(note the spelling 'user' and not 'usr')
in this i discovered two sub-directories:
include lib
the contents of these directories as follows:
# ls include
sigc++-1.2
# ls lib
libsigc-1.2.a libsigc-1.2.so libsigc-1.2.so.5.0.5 sigc++-1.2
libsigc-1.2.la libsigc-1.2.so.5 pkgconfig
wonder where all this came from, could it have been a typo by the
developer who made the scripts for compiling libsigc++, or is this by
design?
??
LL
_______________________________________________
ilugd mailing list
[EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd
