On Fri, 2005-06-03 at 08:10 -0400, gslink wrote:
There were a number of update rpms recently posted for gcc. One way to cause this problem is to omit loading one of them. This happened to me and I believe that one of the updates was not posted with the others. All the updates are there now. The easiest way to check for this problem is to set up a kernel source. If that shows errors when you run rpmbuild then this is the likely cause.
# rpm -qa|grep gcc libgcc-4.0.0-9 gcc-4.0.0-9 gcc-c++-4.0.0-9 gcc-java-4.0.0-9
yum reports no new packages..
-HK