/lib/libgcc_s.so.1(*IND*+0x0): multiple definition of `__divdi3@GLIBC_2.0'

[Shawn]

No, and I upgraded to the latest binutils snapshot in the gcc-3.2.2
home, and things are more dandy now.

It appears binutils 2.13.90.0.2 from redhat is insufficient to run
glibc-2.3.2, which is not indicated in the INSTALL file.

Maybe some earlier 2.13.x binutils works, but not that one.

On Sun, 2003-03-16 at 00:58, Andreas Jaeger wrote:
> Shawn <core@enodev.com> writes:
> 
> > I am having a problem just after installing glibc-2.3.2 on Redhat 8.0
> > (after fixing the issues in /lib/i686/lib*)
> 
> This looks like some broken setup of your new GCC (libgcc_s.so.1 comes
> from GCC).  Does this work with Red Hat's GCC and Red Hat's
> libgcc_s.so.1 from their GCC package?
> 
> The general advise of us is to not upgrade glibc yourself, there're to
> many ways to shoot yourself :-( and I don't see directly what you have
> done wrong.
> 
> Andreas