Re: Shared library version numbers [Was: LSB inclusion of OpenSSL]

2005-10-31 Thread Andy Polyakov
... in PAM case I can imagine problem with GLOBAL_OFFSET_TABLE being "cross-polluted" by 0.9.7 and 0.9.8 being *both* mapped into same application. Is it the case? Can you elaborate on which symbols were overloaded? You can figure this out by examining dynamic name tables *in pam modules* with

Re: Shared library version numbers [Was: LSB inclusion of OpenSSL]

2005-10-31 Thread Andy Polyakov
But I'll take up the cue and see what we can do that works everywhere. Then it would have to be the least common denominator: 97, 98, 100 or independent numbers such as 1, 2, 3. The above was referring to file suffixes. It should be noted that there're platforms, which has no notion of vers

Re: Shared library version numbers [Was: LSB inclusion of OpenSSL]

2005-10-30 Thread Kurt Roeckx
On Fri, Oct 28, 2005 at 09:46:30AM +0200, Andy Polyakov wrote: > > Now question to Johnny Lam [who is complaining that we don't bump > versions] and Christoph Martin [who suggests to add versioning on all > symbols]. What exactly didn't work for you? As far as I understand both > NetBSD and Deb

Re: Shared library version numbers [Was: LSB inclusion of OpenSSL]

2005-10-29 Thread Kurt Roeckx
On Sat, Oct 29, 2005 at 02:45:51PM +0100, [EMAIL PROTECTED] wrote: > Hi, > > > > If you "simply" use the "-Bsymbolic" flag when building libA, doesn't > > > that solve the problem as well? And in a more portable way, since > > > vrsioned symbols don't exist on "many" platforms? > > > AFAI

Re: Shared library version numbers [Was: LSB inclusion of OpenSSL]

2005-10-29 Thread Stefan . Neis
Hi, > > If you "simply" use the "-Bsymbolic" flag when building libA, doesn't > > that solve the problem as well? And in a more portable way, since > > vrsioned symbols don't exist on "many" platforms? > > AFAIK, the idea of the flag is that the library doesn't automatically > > doesn't r

Re: Shared library version numbers [Was: LSB inclusion of OpenSSL]

2005-10-29 Thread Kurt Roeckx
On Sat, Oct 29, 2005 at 03:12:24AM +0100, [EMAIL PROTECTED] wrote: > Hi, > > > Then when the dynamic linker looks for a symbol, it looks at it > > by name. It will go over all objects to see if it exists in it. > > It will use the symbol from the first library it finds it in. > > > > This

Re: Shared library version numbers [Was: LSB inclusion of OpenSSL]

2005-10-28 Thread Stefan . Neis
Hi, > Then when the dynamic linker looks for a symbol, it looks at it > by name. It will go over all objects to see if it exists in it. > It will use the symbol from the first library it finds it in. > > This means, that a symbol that libA requires, and _should_ get > from libssl.so.0.9.7

Re: Shared library version numbers [Was: LSB inclusion of OpenSSL]

2005-10-28 Thread Kurt Roeckx
On Fri, Oct 28, 2005 at 09:46:30AM +0200, Andy Polyakov wrote: > > Now question to Johnny Lam [who is complaining that we don't bump > versions] and Christoph Martin [who suggests to add versioning on all > symbols]. What exactly didn't work for you? As far as I understand both > NetBSD and Deb

Re: Shared library version numbers [Was: LSB inclusion of OpenSSL]

2005-10-28 Thread Andy Polyakov
Please note that there is explicit question to couple of subscribers posed in this message. Others should feel free to correct and complement. Right now, we have it depend on the version number. An please tell what the correct format for a soname is. On some Unixen, it seems like the correct