This is the mail archive of the
mailing list for the glibc project.
Re: binutils requirement
- From: "Davin McCall (EAA)" <Davin dot McCall at ericsson dot com dot au>
- To: roland at redhat dot com, drow at mvista dot com
- Cc: libc-alpha at sources dot redhat dot com
- Date: Tue, 25 Mar 2003 13:50:38 +1100
- Subject: Re: binutils requirement
> > I built glibc using binutils 2.12.1 on i386-linux today (it was a bit of an
> > accident, really...). It turns out that it doesn't work; you end up with
> > two symbols named __udivdi3 at GLIBC_2 dot 0, one hidden and one not. Should we
> > be checking the version at configure time?
> There is a configure check. Please figure out why it failed to catch your
> as and/or ld.
This problem might have more to do with gcc than with binutils. I recall
having similar problems some while back when I was compiling with a gcc
which had been built against the old binutils, even though I was using
newer binutils to compile glibc. In my case, recompiling gcc (against
the new binutils) solved the problem.
I'm not sure about this so please take this as a suggestion for
something to look at if nothing else seems to make sense.