🚀 go-pugleaf

Reposting this for Jim, whose poster is broken.

From Jim.Vishoot@telematics.com.au  Fri Mar 26 07:29:51 1993
Return-Path: <Jim.Vishoot@telematics.com.au>
Subject: Re: Anyone using gcc cross to MIPS ?
Newsgroups: gnu.gcc.help
Organization: Telematics International, Inc. - Ft. Lauderdale, FL

In article <3273@rhino.qpsx.oz.au> you write:
>I have just installed gcc-2.3.3 and see that I cannot use it to cross
>compile to MIPS because mip-tdump.c and mip-tfile.c can only be compiled
>on a MIPS machine. Has anyone out there solved this problem ? What are
>people using for MIPS cross compilation. IDT sell IDT/c but it looks
>very much like gcc with very little else added.
>
>We would like to be able to use g++/gcc for our cross development environment.
>
>thanks,
>davidp.


You only need mips-tdump and mips-tfile if you are using the MIPS
assembler (i.e., on a MIPS platform). GCC can be configured to
generate assembly for GAS (the default, I suppose). I believe GAS 2.0
includes support for the MIPS cpu, so all you need is a
linker...there's GNU LD (of course) in the binutils distribution,
although you might be able to use your native ld if you can configure
GAS to generate the same object format. And for the odd bug which
crops up now and then, use GDB which likewise must be configured for
the same object format. And now a word from our sponsor ....

Seriously, we've been using this tool chain (GCC-GAS-GLD-GDB) for at
least six months on Sparcs running SunOS 4.1.3 to cross develop for an
embedded MIPS target (IDT 305x) with a fair amount of success.

By the way, make sure GCC is configured to generate the right kind of
debugging info for whatever debugger you plan to use. Makes life alot
simpler. 

Jim Vishoot
Telematics International, Inc.