> >Well you installed glibc-2.0.112 over glibc-2.0.111 That's okay! They
> >have different version numbers. I installed glibc-2.0.7 over glibc-2.0.7
> >The new one was compiled with a different C compiler. Same version number
> >different code.
>
> Then you will almost certainly come to grief. Modifying a shared library
> while it's in use is a sure way to disaster. This is one of the reasons it's
> not recommended for random users to upgrade their glibc.
>
Well I've been called a lot of things, but not a "random user" before ;)
I don't think I should have to recompile all the tools to `static` if I
wish to rebuild glibc with the "latest-and-greatest" compiler. This
problem is certainly going to come up again. If the developers of ld.so
would respond, maybe its as simple as renaming ld.so.cache before
`make install`.
Cheers,
Dick Johnson
***** FILE SYSTEM WAS MODIFIED *****
Penguin : Linux version 2.2.1 on an i686 machine (400.59 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.
Wisdom : It's not a Y2K problem. It's a Y2Day problem.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/