Share object (libstdc++) - Software release question.

[Joerg Faschingbauer]

>>>>> "Martin" == Martin v Loewis <martin@loewis.home.cs.tu-berlin.de> writes:

>> I build a shared object which is dynamiclly linked with libc++.so.2.8.1.
>> Now I give this shared object to a customer, say the customer has a higher 
>> version of libc++.so.2.9.xx.
>> What have I got to do?
>> Ask the customer install the old libc++.so.2.8.1?
>> or I build another shared object linked with libc++.so.2.9.xx just for this 
>> customer.
>> What is a better way than both of above?

Martin> Both approaches solve your problem, and nothing else would work.

Martin> If that is an option, I'd recommend to upgrade to the current version
Martin> of gcc, which is 2.95.2; that comes with libstdc++ 2.10. It is
Martin> possible that other customers of you will also find a need to install
Martin> gcc 2.95.x over time, in which case you'd be prepared to respond.

Another option would be to link the shared object with libstdc++.a
statically. This way you are independent of any changes to libstdc++,
of course at the price of a larger binary.

Joerg