....
CodeSourcery is "for" Coldfire which (I think) has a richer
instruction set than the 68000 cpu I have.

Hi,

I'm using the free Code Sourcery Lite gcc for m68k for a home project
that involves a micro with 68000 cpu core. I added -lgcc to the
linker flags to resolve an issue with __divsi3.

If this is true and that
lib is built with that instruction set, it wouldn't be compatible with
my object code. I think this is what the error is saying.

Jim wrote:
Hi,

I'm using the free Code Sourcery Lite gcc for m68k for a home project
that involves a micro with 68000 cpu core. I added -lgcc to the
linker flags to resolve an issue with __divsi3.

That should never be necessary. GCC already puts -lgcc into the linker
command line it builds, whenever that serves a useful purpose.

If this is true and that
lib is built with that instruction set, it wouldn't be compatible with
my object code. I think this is what the error is saying.

More to the point, GCC would probably have to be built with multilib
support to allow switching between incompatible variants of the same
basic CPU architecture. That would include multiple copies of libraries
such as libgcc, the Standard C++ runtime, and startup code as needed,
and the gcc driver program would automatically pick those needed for the
chosen architecture.

For whatever reasons, your GCC apparently wasn't built that way. Maybe
you need to pick a different package. Or, who knows, you may even have
to bite the bullet and build your own GCC tool chain.

First, I'd like to thank everyone for their input! Second, I'd like
to answer some of the questions so no one feels left out:

- The target cpu is truly a 68000 core (the old Dragonball EZ328).
Now, to avoid the "why": it's a Palm pda which has a display and
formfactor that I need and it's cheap.

Second, I'll see if I can build libgcc. I assume I'll get the source
to this when I download the source to gcc.

Well, thanks again for your help everyone. I'll post what I finally
end up with (in case anyone else needs the info).

First, I'd like to thank everyone for their input!  Second, I'd like
to answer some of the questions so no one feels left out:

- The target cpu is truly a 68000 core (the old Dragonball EZ328).
Now, to avoid the "why":  it's a Palm pda which has a display and
formfactor that I need and it's cheap.
- I'm using my own OS on the embedded system (no Linux).

...text deleted for brevity...

So, I think the general consensus is I only get ColdFire micro support
with CodeSourcery and I agree with this.  I can understand why
CodeSourcery may want to ignore older cores.  However, don't they
still make micros with that (68000 based) core?  I might email them,
but since I'm using the free version, I feel funny bothering them with
this (they do need to earn a living).  Purchasing it would be a real
gamble since they do say it's a ColdFire compiler on their website
(and for home use, it's kinda a pricey gamble).

I'm gonna try two things.  First, I'll look for other precompiled
binaries for MS Windows.  Maybe I'll luck out.  I came across one the
other day, but now can't remember for the life of me who made it--I'm
sure it'll turn up in a search.

Second, I'll see if I can buildlibgcc.  I assume I'll get the source
to this when I download the source to gcc.  David suggested I use
MinGW.  I'm pretty sure I'll need "configure" and maybe autoconf &
automake.  I'm not familiar with MinGW:  does that package have them?

I just got an idea.  PrcTools was a MS Windows compiler for that very
micro.  I remember trying it, but it was a limited 16b compiler trying
to be compatible with the Palm OS.  However, I might be able to use
itslibgcc.  The only issue is that compiler is so old it's probably
COFF based (and of course CodeSourcery is ELF).  Nothing's ever
easy.  :)

Well, thanks again for your help everyone.  I'll post what I finally
end up with (in case anyone else needs the info).

Jim