transition from 2.9 to 2.10 goes pretty smooth
Carlos O'Donell
carlos@systemhalted.org
Mon Jun 22 19:26:00 GMT 2009
On Mon, Jun 22, 2009 at 12:05 PM, Justin Mattock<justinmattock@gmail.com> wrote:
> So the best way is to use a livecd
> mount the partition, compile
> and install libc to it's appropriate
> destination.
Yes.
> Now uninstalling an old version of libc
> I would simple just manually delete the old .so's
> that are just sitting there?
> Header files can probably
> stay there(or delete them, and reinstall)
No, it's more complicated than this. You should undo everything that
the install does, fixing symlinks from libc.so to the old libc etc.
> What about things like(for example)
> If I compiled some app with
> libc 2.9, and them updated libc
> to 2.10 and then delete 2.9
> will that app still work, or does it
> need to be recompiled with 2.10?
> (so the app doesn't segfault)
Applications compiled against an old version of libc will work with a
new version of libc, this concept is called backwards compatibility,
and glibc is backwards compatible (to a point).
Cheers,
Carlos.
More information about the Libc-help
mailing list