[Fwd: [Fwd: Where are _modsi3.c and/or _modsi3.o?]]

[Fwd: [Fwd: Where are _modsi3.c and/or _modsi3.o?]]

[Christopher Bahns]

Ok, sorry. I thought I tried using "-m68000", but I think I tried "-Wl,-m68000" and it
complained that it was not recognized by the linker. If I put "-m68000" as an argument
directly to gcc, then all is well and I don't have to shuffle any files around!

Thanks! much helpful sir
Chris

BTW, to Francisco Rodriguez, ignore what I said about having to move files around. If the
68360 does in fact have a cpu32 core, then you probably want to invoke the linker with
something like:

/gcc-m68k/bin/m68k-coff-gcc -mcpu32 -Wl,-T<program>.ld -Wl,-Map=<program>.map -o
<program>.hex <object files>

Much easier I think.

Doug Evans wrote:

> Christopher Bahns writes:
>  > My question now is:
>  > How can I link to the libgcc.a in the m68000 subdirectory without deleting the one
>  > in the parent directory?
>
> You're not specifying the command you're using to do the link
> [at least I don't recall seeing it].
>
> Assuming you're using gcc to do the link (which you should be doing :-),
> specify -m68000.
>
> The -m68000 tells gcc what cpu to generate code for, but it ALSO
> tells gcc what libgcc to use with that generated code.
>
> [It may be that you're not developing for the m68000 exactly.
> I'm not up on all the m68k variants and the current state
> of gcc support for them, but in principal the above is correct.]
>
> ------
> Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com