Hi guys,
We have an Intel P-4 machine running Redhat 8. Since some packages don't get compiled without glibc 2.3, we decided to upgrade glibc from 2.2.93 to 2.3.2-11.9. We downloaded source rpm from redhat and compiled it on our machine. It created rpms for i386 architecture.
We could upgrade glibc-common and glibc without any problem ( we took the backup of /lib before upgradation). But rpm gives segmentation fault now whenever we try to upgrade or install any package. All other programs seem to be working fine with new glibc.
As it seems, rpm-4.1-1.06 is incompatible with glibc 2.3 and should be upgraded before upgrading glibc. But as we have already done the mistake, please suggest us how can we get rpm working, so that we can upgrade rpm before glibc.
Referring to the comment on:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=89135
we don't have /lib/tls on our machine.
Thanks and Regards,
Manu Garg,
*****************************************************************************************************************************
DISCLAIMER: The information contained in this message is intended only and solely for the addressed individual or entity indicated in this message and for the exclusive use of the said addressed individual or entity indicated in this message (or responsible for delivery of the message to such person) and may contain legally privileged and confidential information belonging to Tata Consultancy Services. It must not be printed, read, copied, disclosed, forwarded, distributed or used (in whatsoever manner) by any person other than the addressee. Unauthorized use, disclosure or copying is strictly prohibited and may constitute unlawful act and can possibly attract legal action, civil and/or criminal. The contents of this message need not necessarily reflect or endorse the views of TATA Consultancy Services on any subject matter. Any action taken or omitted to be taken based on this message is entirely at your risk and neither the originator of this message nor Tata Consultancy Services takes any responsibility or liability towards the same. Opinions, conclusions and any other information contained in this message that do not relate to the official business of Tata Consultancy Services shall be understood as neither given nor endorsed by Tata Consultancy Services or any affiliate of Tata Consultancy Services. If you have received this message in error, you should destroy this message and may please notify the sender by e-mail. Thank you. *****************************************************************************************************************************
Sometime Today, Manu.Garg@seepz.tcs.co.in assembled some asciibets to say:
upgraded before upgrading glibc. But as we have already done the mistake, please suggest us how can we get rpm working, so that we can upgrade rpm before glibc.
you can install rpm from its tarball, maybe in /usr/local/ then use this /usr/local/rpm to install the new rpm from its rpm.
we don't have /lib/tls on our machine.
you could also install this from source tarball, but it may be found in /usr/lib/tls and not in /lib/tls. Very unlikely to find networking libraries in /lib
On Wednesday 04 Feb 2004 11:42 pm, Philip S Tellis wrote:
you can install rpm from its tarball, maybe in /usr/local/ then use this /usr/local/rpm to install the new rpm from its rpm.
Wondering if he will have dependencies problems with this, (and probably leave using RHL after that). Hope both the different versions of RPM's can use the same rpm database. Waiting to know the results if you do use this solution.