Tech Support banner

Status
Not open for further replies.
1 - 2 of 2 Posts

·
Registered
Joined
·
1 Posts
Discussion Starter · #1 · (Edited)
Currently i have a redhat 7.3 box located at a remote location and an "associate" broke glibc. They had the bright idea to update it to the current glibc for redhat 9. Of course..they ended up doing rpm --force --nodeps and hosed most of the box. sshd stopped working untill a complete restart of the daemon, rpm's will not install, uninstall or update and most programs wont even compile.

i've tried compiling the source .tar.gz of glibc to no avail, it error's out each time. rpm's segfault each time

rpm -ivh freenet6-0.9.7-1.i386.rpm
Preparing... ########################################### [100%]
Segmentation fault

It does this with all rpm's not just freenet..


#glibc-2.2.5's make
syslog.c: In function `vsyslog':
syslog.c:219: `cancel_handler' undeclared (first use in this function)
syslog.c:219: (Each undeclared identifier is reported only once
syslog.c:219: for each function it appears in.)
syslog.c:219: warning: type defaults to `int' in declaration of `__save_FCT'
syslog.c:272: called object is not a function
syslog.c: In function `openlog':
syslog.c:330: parse error before `)'
syslog.c:330: `__save_FCT' undeclared (first use in this function)
syslog.c:330: parse error before `)'
syslog.c:338: `__save_ARG' undeclared (first use in this function)
syslog.c: In function `closelog':
syslog.c:362: parse error before `)'
syslog.c:362: `__save_FCT' undeclared (first use in this function)
syslog.c:362: parse error before `)'
syslog.c:372: `__save_ARG' undeclared (first use in this function)
make[1]: *** [syslog.o] Error 1
make[1]: Leaving directory `/usr/local/src/glibc-2.2.5/misc'
make: *** [misc/subdir_lib] Error 2





I'm hoping to avoid a 12 hour trip to the location..so if anyone has any ideas, i'll be very gratefull. thanks in advance
 

·
Registered
Joined
·
711 Posts
ouch... I hope you have thoroughly beaten sense into your associate :bandit: If you have a copy of the CD in the cdrom on the machine in question you might be able to re-install the originally glibc but its highly doubrful that you'd be that lucky in terms of setup. You might grab the original glibc and rpm packages and try to forcebly reinstall them or upgrade RPM ... perhaps build it against another box with a similar config and just replace the binary instead of trying to install it via rpm...

Good Luck!
 
1 - 2 of 2 Posts
Status
Not open for further replies.
Top