CrossGCC bug?

[Tomaz Stih]

I've never actually encounter this problem and I am not ready to
put my hand in fire for this information but seems like a recursive 
problem with libgcc1. Somewhere I read that libgcc and libgcc1 are
required to properly compile c programs which include operations that are
not directly supported by the target system. Thus if you compile
libgcc1 with gcc calls to these functions they will compile into 
recursive call to themselves.

Does anyone know what is the difference between gcc and gcc1 libs?
When I compile m68k-coff tools I don't get libgcc1. Is this okay?

Lp,
tomaz

libgcc1.a. So I have to make libgcc1.a manually. Then when I do the
make, I get:
/bitbucket/cheng2/build-gcc/../gcc-2.7.2.2/libgcc1-test.c:20: undefined
reference to `__divsi3'
/bitbucket/cheng2/build-gcc/../gcc-2.7.2.2/libgcc1-test.c:21: undefined
reference to `__modsi3'
/bitbucket/cheng2/build-gcc/../gcc-2.7.2.2/libgcc1-test.c:23: undefined
reference to `__udivsi3'
/bitbucket/cheng2/build-gcc/../gcc-2.7.2.2/libgcc1-test.c:24: undefined
reference to `__umodsi3'