Groups > comp.os.linux.development.apps > #437

Re: libc versioning question

From	Lusotec <nomail@nomail.not>
Newsgroups	comp.os.linux.development.apps
Subject	Re: libc versioning question
Followup-To	comp.os.linux.development.apps
Date	2012-02-27 17:23 +0000
Organization	A noiseless patient Spider
Message-ID	<jige65$uc4$1@dont-email.me> (permalink)
References	<jieghq$c37$1@dont-email.me> <jift39$n22$1@dont-email.me> <87sjhwdzi2.fsf@sapphire.mobileactivedefense.com>

Followups directed to: comp.os.linux.development.apps

Show all headers | View raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Rainer Weikusat wrote:
> Lusotec writes:
>> Cat22 wrote:
>>> I have a (precompiled) program that requires libc 2.11 but i only
>>> have libc 2.10. Is it practical or even possible to put the 2.11 files
>>> in some directory then run the program using the LD_LIBRARY_PATH
>>> environment variable so it would use the 2.11 versions? I dont think you
>>> can just upgrade libc and libstdc++ on my system without wreaking havoc
>>> can you? I do some C programming from time to to time, but I have not
>>> had to really ever consider the versions of these libs in the past so I
>>> just dont know what can or cant be done there.
>>> Thanks
>>> Cat22
>>
>> Upgrading libc 2.10 to libc 2.11 (a minor version upgrade) should not
>> cause any issues.
> 
> The problem with this is that the outcome of such an experiment isn't
> known until after it was conducted and it is not usually reversible.

If Cat22 only points the symlink /lib64/libc.so.6 to the new library, it 
should be easy to reverse. I don't foresee any issues. On the Mandriva 
systems I use and administer, the libcs have been updated many times without 
any issues.

Still, you are right in that problems are not impossible. Upgrade problems 
are one of the reasons why having up-to-date backups is a very good idea.

Regards.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iF4EAREIAAYFAk9LvAQACgkQGQjO2ccW76q34gD/Xux92XDQ6OvqMiNAHZn9WYYb
cYSm+p7+86vp0CTdHe0A/jiBxhVKF4fcfS1slymiwYeK0HOup/KrNp0AbPAzsHrq
=jX4i
-----END PGP SIGNATURE-----

Back to comp.os.linux.development.apps | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

libc versioning question Cat22 <cat22@invalid.org> - 2012-02-26 15:51 -0800
  Re: libc versioning question Lusotec <nomail@nomail.not> - 2012-02-27 12:31 +0000
    Re: libc versioning question Rainer Weikusat <rweikusat@mssgmbh.com> - 2012-02-27 16:15 +0000
      Re: libc versioning question Lusotec <nomail@nomail.not> - 2012-02-27 17:23 +0000
        Re: libc versioning question Cat22 <cat22@invalid.org> - 2012-02-28 00:49 -0800
        Re: libc versioning question Richard Kettlewell <rjk@greenend.org.uk> - 2012-02-28 09:24 +0000
        Re: libc versioning question Rainer Weikusat <rweikusat@mssgmbh.com> - 2012-02-28 14:47 +0000
  Re: libc versioning question John Reiser <jreiserfl@comcast.net> - 2012-02-28 08:06 -0800

csiph-web