In debian, libncurses.so is not installed unless libncurses-dev is
also installed. Therefore, programs should open libncurses.so.5
directly.
No. Ideally the installation script for your program would create a
symlink from a private directory for your program to the libncurses that
your pro
Hi,
Paolo Bonzini schrieb:
In debian, libncurses.so is not installed unless libncurses-dev is also
installed. Therefore, programs should open libncurses.so.5 directly.
No. Ideally the installation script for your program would create a
symlink from a private directory for your program to th
The only way I see that happen in a sane way is to have all three
libtool version numbers passed to a new lt_dlopenadvise API (CVS HEAD)
and have libltdl compute the soversion from there.
Yes, that's a good idea for the interface. But the implementation is no
less of a mess. First, as you p
Hello Paolo,
* Paolo Bonzini wrote on Mon, Dec 10, 2007 at 09:44:55AM CET:
> In debian, libncurses.so is not installed unless libncurses-dev is also
> installed. Therefore, programs should open libncurses.so.5 directly.
And on Solaris, the program should know that libncurses.so.5 on
GNU/Linux h
In debian, libncurses.so is not installed unless libncurses-dev is also
installed. Therefore, programs should open libncurses.so.5 directly.
However, this is not possible with ltdl_openext. Would a patch be
accepted to extend ltdl_openext("libncurses.5") like this:
- of course, opening "lib
