-
/lib/ld-linux.so.2 points to /lib/ld-2.3.5.so which exists.
The error happened while glibc was 'make && make install' (I know, it was silly of me, I should have split both operations).
I have no idea what I should relink from /usr/local/lib to /usr/lib since I gathered the glibc install would do it for me.
I don't think I have the option of uninstalling, either, as I've played around too much with the source/build directories since the original installation.
-
Well, the problem wasn't during the make, I would assume. Because the way && works is that the secondary command will not be executed unless the first command completes without error. Seperating the process wouldn't have prevented the error so I wonder if it was during the compilation process since make -had- to have completed successfuly for make install to even run.
-
Yeah, it's bound to have happened during the make install, but still, it's silly.
It looks like now I am going to have to go deus ex machina on the box and compile an older glibc; unless I can figure out which links exactly it is looking for and modifying them.. Any idea how to trace that kind of stuff?
-
Okay, I think I completely broke it; well, at least, it's beyond my means to fix this, so I'm gonna start over. At least now I have a path I can follow... Right? ;-)
-
Well, I'm back where I started.. sort of.
I made a snapshot (thank you vmware!) before installing glibc-2.3.5 but when I do compile it, I get that same problem; so I think I need a crash course in upgrading glibc.. Or am I gonna need to upgrade it progressively, which would suck, but make sense.. ?
-
Oh, Christ. Let me guess.. I need to install the new glibc versions progressively and recompile against the new versions until I get to a 2.3 or something.. And that means I need to do this with the old version of gcc first.. So it has to be done, weaved into the rest of the installation. That's too much hell for me ;-) A merry christmas to all, and to all a good +++NO CARRIER+++