GLIBC and Backward Compatibility

GLIBC and Backward Compatibility

Post by Michael Malone » Fri, 31 Jan 2003 10:05:41



I am developing an app using RH 8.0. I then distribute the binaries
to my users, some of whom are still using RH 7.3.
Recently when I sent out an upgrade, the 7.3 users got the error:
/lib/libc.so.6: version 'GLIBC_2.3' not found (required by .... <my SO
library name>)

How can I compile my application code so that it will be backwardly
compatible for the 7.3 (and 7.1) users?

Are there compile options or #defines I can use?

 
 
 

1. Backward compatibility and GLIBC

I am developing an app using RH 8.0. I then distribute the binaries
to my users, some of whom are still using RH 7.3.
Recently when I sent out an upgrade, the 7.3 users got the error:
/lib/libc.so.6: version 'GLIBC_2.3' not found (required by .... <my SO
library name>)

How can I compile my application code so that it will be backwardly
compatible for the 7.3 (and 7.1) users?

Are there compile options or #defines I can use?

2. Printer Problem !?!

3. 4.8-R libc stdio backward binary compatibility

4. upgraded to kde 2.2, tuxtime no longer autostarts

5. backward compatibility between 2.5 and 2.4

6. Reverse rm

7. Help: backward compatibility problems with SunOS 5.1

8. what is module net-pf-4?

9. C compiler backward compatibility

10. Backward compatibility of linux libraries?

11. Solaris7 backward compatibility question

12. GCC and backward compatibility: Solaris 2.6 -> 2.5

13. HP DDS2 and DDS3 backward compatibility