Using a shared library to partly replace an archive library - ld changed behaviour

[Dave Korn]

----Original Message----
>From: H. J. Lu
>Sent: 26 April 2005 16:55

> On Tue, Apr 26, 2005 at 03:27:13PM +0100, Graham Hudspith wrote:

>> undefined symbols. When the application invokes one of the "first set of
>> functions", these are caught and implemented by the ARCHIVE library
>> which then goes on to call one of the "second set of functions", also
>> from the archive library.  Our shared library is ignored. If we build
>> our shared library by linking it into the archive library first,
>> everything works fine, but this is not what we want.
>> 
> 
> I am not sure if I understand what you are saying. 


  I think he's perhaps saying that his users should be compiling their
static libraries with weak symbols, isn't he?


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....