Dear Jakub,
Thanks for your response.
No, it was not rawhide. I never use rawhide.
It turns out that I had inadvertently included two "testing"
repos in /etc/yum.repos.d, which turned out to have available
glibc-2.4.90
glibc-common-2.4.90
and
glibc-headers-2.4.90
which yum check-update found so I updated them.
However gcc uses glibc-devel, which still is version 2.4-8,
which does not work with the later versions listed above for
the other glibc packages. (This was not detected by yum!)
So laboriously, using straight rpm -Uvh --oldpackage (I don't
know how to make yum install old packages), I replaced the
three listed above with 2.4-8 versions, and re-installed
gcc-4.1.1-1.fc5 (and the similar gcc-g++), and now everything
works.
Oh, of course I also deleted the "testing" repos from
/etc/yum.repos.d, a lesson for the day.
-- Peter
=====================================================
On Aug 09, 2006 at 1:51 am, Jakub Jelinek wrote:
| On Tue, Aug 08, 2006 at 05:37:32PM -0700, Peter Scott wrote:
| > I have experienced a recent problem: After updating glibc
| > (using yum update glibc) I'm finding I can no longer compile C
| > programs; they fail to link, yielding the error message
| >
| > /usr/lib/../lib64/libm.so: file not recognized: File format
| > not recognized
| > collect2: ld returned 1 exit status
|
| That sounds like you upgraded to rawhide glibc on FC5; don't do that.
| You'd need to upgrade several other packages as well, at least binutils,
| prelink, gdb, elfutils.
|
| Jakub
|
| --
| fedora-list mailing list
| fedora-list@xxxxxxxxxx
| To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
|
