However, you can install the libc5 compatibility stuff and then the
old stuff should work. Actually, I thought this would be installed by
default. Is it not?
>First off - this was possibly an unwise thing to do, since RH5
>introduced libc6, which is a pretty major change. I think treating
>that move as an "upgrade" is a mistake.
>However, you can install the libc5 compatibility stuff and then the
>old stuff should work. Actually, I thought this would be installed by
>default. Is it not?
What, specifically broke?
--
Unix had startmenus and taskbars before Microsoft |||
even had a decent memory manager for DOS. / | \
In search of sane PPP docs? Try http://penguin.lvcm.com
1. Redhat backward compatibility
I upgraded RedHat 4.2 to RedHat 5.1 on one of our machines. Lots of
programs stop running after that. Most of time, it is because some of the
dynamic library files for 4.2 do not exist any more in 5.2 system.
I know everything should be all right if I can recompile everything. But
it is not always easy to do that. So I like to know if
anyone knows any easy way to make 5.1 backward compatible with 4.2?
Do I have to copy all those 4.2 library files to the 5.2 system which
does not seem to be the right way to do? Thanks a lot.
3. US-CA-El Segundo Unix Sys Admin openings
4. 4.8-R libc stdio backward binary compatibility
5. IBM ISA Etherjet NIC Driver
6. backward compatibility between 2.5 and 2.4
8. GLIBC and Backward Compatibility
9. Help: backward compatibility problems with SunOS 5.1
10. C compiler backward compatibility
11. Backward compatibility of linux libraries?
12. Solaris7 backward compatibility question