Tried to do a yum update for rawhide and it hangs. There appears to be something wrong with /sbin/ldconfig from glibc-2.16.90-24.fc19.x86_64.rpm. Every yum update I do now hangs while trying to do an /sbin/ldconfig and if I try to update via rpm and then attach an strace to the pid doing the ldconfig ldconfig cores and the update continues (probably not the behaviour we want to see). Is there a newer version of glibc available and/or what changed in ldconfig?
Regards,
------------------------ Kevin Martin
On 10/17/12 11:53, Kevin Martin wrote:
Tried to do a yum update for rawhide and it hangs. There appears to be something wrong with /sbin/ldconfig from glibc-2.16.90-24.fc19.x86_64.rpm. Every yum update I do now hangs while trying to do an /sbin/ldconfig and if I try to update via rpm and then attach an strace to the pid doing the ldconfig ldconfig cores and the update continues (probably not the behaviour we want to see). Is there a newer version of glibc available and/or what changed in ldconfig?
Regards,
Kevin Martin
ok, more info. I found (by stracing /sbin/ldconfig) that it was failing as a result of the following 3 libraries in /usr/lib64 not being linked correctly:
libboost_thread-mt.so libopcodes.so libbfd.so
Once I rm'd those files and linked them (as shown below) ldconfig ran to completion just fine.
ln -sf /lib64/libboost_thread-mt.so.1.50.0 /lib64/libboost_thread-mt.so ln -sf libopcodes-2.23.51.0.3-1.fc19.so libopcodes.so ln -sf libbfd-2.23.51.0.3-1.fc19.so libbfd.so
Now a yum update from 3-4 days ago updated boost-devel and binutils-devel which is where those libraries come from. Somebody needs to take a look at the boost-devel-1.50.0-4.fc19.x86_64 and the binutils-devel-2.23.51.0.3-2.fc19.x86_64 rpm's and make sure that the linking is correct.
Thanks again.
Kevin
Just as a datapoint I am not seeing this on my rawhide instance... ;(
So, not sure if it was an issue because I missed a days updates or what.
kevin
On 10/17/12 12:34, Kevin Fenzi wrote:
Just as a datapoint I am not seeing this on my rawhide instance... ;(
So, not sure if it was an issue because I missed a days updates or what.
kevin
It looks like it's not necessarily related to rpm-libs in particular but only to the fact that the boost-devel and binutils-devel rpms don't seem to be linking some files in /usr/lib64 correctly. Running a yum update now and I'm experiencing the same issue as I was and binutils-devel was one of the updates (I was hoping it was an update that was fixing the linking problem but it doesn't appear to be the case). After the binutils-devel update I had to relink the two .so files again and then strace the ldconfig that was running to get it to core (should it do that or is that a bug?) so the yum update could move forward....now it's hung trying to update valgrind but I don't know why. I think I'm going to kill the yum update and run it again with some verbosity to see if I can see where it's getting hung up.
Kevin
On Wed, 17 Oct 2012 14:09:52 -0500 Kevin Martin ktmdms@gmail.com wrote:
It looks like it's not necessarily related to rpm-libs in particular but only to the fact that the boost-devel and binutils-devel rpms don't seem to be linking some files in /usr/lib64 correctly. Running a yum update now and I'm experiencing the same issue as I was and binutils-devel was one of the updates (I was hoping it was an update that was fixing the linking problem but it doesn't appear to be the case). After the binutils-devel update I had to relink the two .so files again and then strace the ldconfig that was running to get it to core (should it do that or is that a bug?) so the yum update could move forward....now it's hung trying to update valgrind but I don't know why. I think I'm going to kill the yum update and run it again with some verbosity to see if I can see where it's getting hung up.
Yeah, odd.
I have:
binutils-devel-2.23.51.0.3-2.fc19.x86_64
installed here and it updated fine a bit ago. ;(
kevin