Re: Stupid library ABI question

2007-01-17 Thread Steve Langasek
On Wed, Jan 10, 2007 at 09:36:28AM -0800, Kevin B. McCarty wrote: > > How will applications linked against the original libfoo be able to > > locate the symbols B and C? As these are called directly from the > > application, the application would have to be linked against libbar. > > You are addi

Re: Stupid library ABI question

2007-01-10 Thread Kevin B. McCarty
Neil Williams wrote: > On Wed, 10 Jan 2007 09:36:28 -0800 "Kevin B. McCarty" > <[EMAIL PROTECTED]> wrote: >> Upstream of my library (Cernlib maintainers) only ships static >> libraries, and the shared library support is hacked in by me. So I >> have complete control over the soversion, but of co

Re: Stupid library ABI question

2007-01-10 Thread Neil Williams
On Wed, 10 Jan 2007 09:36:28 -0800 "Kevin B. McCarty" <[EMAIL PROTECTED]> wrote: > Thanks everyone who answered so far! Unfortunately some of the answers > (Steve Langasek's vs. Neil Williams') seem directly opposed :-) In such cases, I defer to vorlon. :-) > > A better solution for libfoo, IMH

Re: Stupid library ABI question

2007-01-10 Thread Justin Pryzby
On Wed, Jan 10, 2007 at 09:36:28AM -0800, Kevin B. McCarty wrote: > Thanks everyone who answered so far! Unfortunately some of the answers > (Steve Langasek's vs. Neil Williams') seem directly opposed :-) I'd > like to try to understand this better since I really know very little > technical deta

Re: Stupid library ABI question

2007-01-10 Thread Kevin B. McCarty
Thanks everyone who answered so far! Unfortunately some of the answers (Steve Langasek's vs. Neil Williams') seem directly opposed :-) I'd like to try to understand this better since I really know very little technical detail about how the runtime linker works. Neil Williams wrote: > On Mon, 08

Re: Stupid library ABI question

2007-01-09 Thread Steve Langasek
Hi Kevin, On Mon, Jan 08, 2007 at 11:19:40AM -0800, Kevin B. McCarty wrote: > I have a dumb library ABI question. Suppose I maintain a library > libfoo.so that has public functions A(), B() and C(). Now there is a > new release in which libfoo.so only provides A(), but it is now (newly) > dynami

Re: Stupid library ABI question

2007-01-09 Thread Goswin von Brederlow
Neil Williams <[EMAIL PROTECTED]> writes: > On Mon, 08 Jan 2007 11:19:40 -0800 > "Kevin B. McCarty" <[EMAIL PROTECTED]> wrote: > >> Hello, >> >> I have a dumb library ABI question. Suppose I maintain a library >> libfoo.so that has public functions A(), B() and C(). Now there is a >> new release

Re: Stupid library ABI question

2007-01-08 Thread Neil Williams
On Mon, 08 Jan 2007 11:19:40 -0800 "Kevin B. McCarty" <[EMAIL PROTECTED]> wrote: > Hello, > > I have a dumb library ABI question. Suppose I maintain a library > libfoo.so that has public functions A(), B() and C(). Now there is a > new release in which libfoo.so only provides A(), but it is now

Re: Stupid library ABI question

2007-01-08 Thread Hubert Chan
On Mon, 08 Jan 2007 11:19:40 -0800, "Kevin B. McCarty" <[EMAIL PROTECTED]> said: > Hello, I have a dumb library ABI question. Suppose I maintain a > library libfoo.so that has public functions A(), B() and C(). Now > there is a new release in which libfoo.so only provides A(), but it is > now (n