Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.development.apps > #438
| From | Cat22 <cat22@invalid.org> |
|---|---|
| Newsgroups | comp.os.linux.development.apps |
| Subject | Re: libc versioning question |
| Date | 2012-02-28 00:49 -0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <jii4eq$k3i$1@dont-email.me> (permalink) |
| References | <jieghq$c37$1@dont-email.me> <jift39$n22$1@dont-email.me> <87sjhwdzi2.fsf@sapphire.mobileactivedefense.com> <jige65$uc4$1@dont-email.me> |
On 2/27/2012 9:23 AM, Lusotec wrote: > -----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----- > I do regular backups, learned that the hard way. I probably should upgrade, but i have made my little tweaks and so on for a long time now and I am reluctant to lose them on an upgrade. What i suppose i could do is install the latest mandriva pp on a new disk and see how it goes. I may try the symlink idea, it seems to be an easily reversible option. I would still need to get a newer versoin of the binaries tho or compile them myself (how big a job is that? not to bad?) Thanks Cat22
Back to comp.os.linux.development.apps | Previous | Next — Previous in thread | Next in thread | Find similar
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