Re: unresolved symbol __udivsi3_i4

From: Geert Uytterhoeven
Date: Fri Sep 24 2004 - 06:16:57 EST


On Fri, 24 Sep 2004, Jan-Benedict Glaw wrote:
> On Fri, 2004-09-24 10:33:12 +0200, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
> wrote in message <Pine.GSO.4.61.0409241031410.27692@xxxxxxxxxxxxxxxxxxxx>:
> > On Fri, 24 Sep 2004, [utf-8] Pawe? Sikora wrote:
> > > On Friday 24 of September 2004 04:10, Donald Duckie wrote:
> > > > can somebody please help me how to overcome this
> > > > problem:
> > > > unresolved symbol __udivsi3_i4
> > > # objdump -T /lib/libgcc_s.so.1|grep div
> > > 000024c0 g DF .text 00000162 GLIBC_2.0 __divdi3
> > > 00002b80 g DF .text 000001ed GCC_3.0 __udivmoddi4
> > > 00002870 g DF .text 00000120 GLIBC_2.0 __udivdi3
> > >
> > > you can link module with libgcc.a or fix it.
> >
> > Just add an implementation for __udivsi3_i4 to arch/sh/lib/. They already have
> > udivdi3.c over there.
>
> Either that (which I don't like!), or have a try compiling the kernel

Why don't you like that? It's done that way on most architectures.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/