Rob Browning <[EMAIL PROTECTED]> writes:
> In my experience, the warnings have come from dangling symlink in the
> lib directories. I'm not sure how they get there.
The dangling symlink could either be from a package which doesn't
include the symlink that ldconfig would create, or because the
li
> Yes, it is discussed in the Debian Packaging Manual, section 12.
> See:
> /usr/doc/dpkg/packaging.html/ch-sharedlibs.html
>
> You should just go ahead and file bugs against packages which don't
> include the .so link as part of the package.
If I understand this correctly, there is no need to
In message <[EMAIL PROTECTED]> you wrote:
[snip]
>Currently, on my 386 system...
>
>ldconfig: warning: can't open /usr/local/lib (No such file or directory),
>skipping
>ldconfig: warning: can't open /usr/lib/i486-linuxaout/libdb.so.1 (No such file
>or direct
>ory), skipping
>ldconfig: warning: ca
Hi,
This is a minor annoyance, but it always bothers
me. When upgrading or reconfiguring, I chronically
end up with "orphaned" lines in /etc/ld.so.conf.
ie.
Currently, on my main Pentium system...
ldconfig: warning: can't open /usr/X11R6/lib/libgtk.so.1.0 (No such file or
directory), skippin
4 matches
Mail list logo
