Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Rainer Weikusat Newsgroups: comp.os.linux.development.apps Subject: Re: libc versioning question Date: Mon, 27 Feb 2012 16:15:01 +0000 Lines: 19 Message-ID: <87sjhwdzi2.fsf@sapphire.mobileactivedefense.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: individual.net zumj6zRa2KPArDOi2iE+yQf+NeLerljSlx1fDLskdb6WmY1ek= Cancel-Lock: sha1:i0PU4X8WOebHhQvndja0dkLueCc= sha1:jm6UEvPGXX2MuCwkJA4GXvJhDcw= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.development.apps:436 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.