|
From: | Reuben Thomas |
Subject: | bug#30402: ldconfig confusion |
Date: | Fri, 9 Feb 2018 21:12:17 +0000 |
Reuben Thomas wrote:
I just noticed that on my GNU/Linux system (and on stock Ubuntu 14.04,
which is where I first encountered this), I need to run
ldconfig
after installing shared libraries built with libtool. I was confused at
first, because libtool itself runs
ldconfig -n $(libdir)
But I guess because this does not update the cache, it doesn't make the
library available.
I'm not sure.
I just run one of my tests - build of binary with shared library and and installation into one system default paths for shared libraries.
Result:
- ldconfig -p does not show new library
- ldd binary shows library
- binary is executed properly
[Prev in Thread] | Current Thread | [Next in Thread] |