Hello everyone (I tried to post some time before but I was not subscribed to the list so I'm not sure it worked).
I am working on a Redhat 7.2 system with "kernel 2.4.19 #2 SMP". I think I broke everything by installing a new version of glibc using the --nodeps option of rpm. I suppose I downloaded wrong versions of the rpms packages I was trying to install. I was in fact stuck with dependencies errors about a missing libc.so.6(GLIBC-2.3). So I tried and forced rpm to install a new version : glibc-common-2.3.2-57.rpm, and the corresponding glibc, glibc-devel, and binutils that were in the same directory on the ftp. But now many things seem broken, and most of all rpm doesn't work anymore : it segfaults everytime I try to do an "rpm -Uvh" or "rpm -ivh", so I can't even replace the glibc with the old version. I badly need to install software on this server, and I cannot afford to reinstall the full OS at all. I have downloaded the src rpm from the old glibc (glibc-2.2.4-32.src.rpm), and extracted the glibc-2.2.4.tar.bz2 which was in /usr/src/redhat/SOURCES after the segfault of rpm on this src package. Then I followed the instructions inside this directory to do: configure --prefix=/usr/local --enable-add-ons and make both of which seem to be successful. Can I solve my problem by doing a manual "make install" in this same directory? Or should I have done something with all those patches that were along before doing the make? More importantly: Is there a chance I will break the system even further by doing this, even screwing rpm completely, since most packages depend on glibc which will be replace by an older version without telling rpm? How else could I repair the system ... and rpm ? Any help will be greatly appreciated. Thanks a lot in advance! Olivier -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
