On Thu, Jul 12, 2001 at 09:40:53PM +0100, Gary Coady mentioned:
> On Wed, Jul 11, 2001 at 10:57:18AM +0100, John P. Looney wrote:
> > Anyone know what the story is with glibc incompatibilities ? I've got a
> > wierd problem where compiling openssl on my redhat (7.1/glibc2.2.2) box
> > works - and I can run the binary, but if I scp it to another box (custom
> > distro/glibc2.2.1) and try and run it, it core dumps, in fputs().
> > Now, if I compile it on a Mandrake (7.2/glibc2.1.3) box, it runs fine on
> > said "custom" box.
>> AFAIK glibc is designed to be forward compatible, but not backward
> compatible. I think the last major incompatiblity jump was with 2.1.97 so
> anything compiled with a later version of libc will not work on a libc
> library below that. Annoying but true.
Er, fputs() not working between 2.2.2 and 2.2.1 is a major problem. Ah,
DLL hell, it's nice to see it's not just on windows.
When I say 'free', I mean 'free': free from bond, of chain or command:
to go where you will, even to Mordor, Saruman, if you desire. "
-- Gandalf, paraphrasing the choice between Free and Non-free software
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!