On Sat, 2018-02-17 at 10:37 +0300, Sergei Golovan wrote: > Well, I know that and I'd like to keep it underlinked in order to make > it possible to link with libtlc8.5 or libtcl8.6 for application which use it.
I see, I was not aware of this. > The libtcl ABI is sufficiently stable and I don't want to restrict libexpect > to any particular version of libtcl. I note that libtcl does not use symbol versioning. In other cases of mixing two versions of a library in the same process without symbol versioning, this results in crashes. Does libtcl ABI avoid these issues? > The libexpect manual explicitly says that any application using libexpect > has to be linked with it and with libtcl. Is this enforced in some way? > If there's another reason why it shouldn't be underlinked I'd be glad > to hear it. Nothing apart for the usual reasons for avoiding underlinking. > CC: [email protected], > tags 890228 + moreinfo > thanks BTW, this is a newer and simpler way to do that: Control: tags -1 + moreinfo -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
