🚀 go-pugleaf

Hi, I'm trying to build a cross-compilation environment on my DECstation to
compile code for a 68030 embedded system (a Cisco router if you're curious).
The router flash loader takes a standard UNIX executable file (there is boot
ROM code that allows you to do a TFTP load) and puts it into flash memory.

Now I don't know a whole lot about Unix a.out and loader formats and stuff like
that.  I have built gcc into a cross-compiler (m68k-sunos was my guess), and I
built the gas 68k assembler.  The biggest problem is building a cross-loader. I
have gnu load, but it obviously (?) can't use my MIPS a.out.h file, because the
target is a different system with a different format (ostensibly).  I got Cisco
to scrounge up an a.out.h file, but then I found an a.out.gnu.h file, which
somewhat confused me.  Well, what I did was I decided to use the a.out.gnu.h
file, and I build the assembler and the loader with the same file.

My problem is that the loader is rejecting the assembler .o file, saying
"malformed input file (not real or archive)".  But I used the same a.out.gnu.h
file for both the assembler and the loader.

What is the proper way to build a cross-loader?  Why am I getting conflicts
between the assembler and the loader?  Has anybody successfully build a
cross-compiler for an embedded system, and how did you do it?

Eric Ewanco
ewanco@kalvin.enet.dec.com

--
/===========================================================================\
| Eric Ewanco - Software Engineer   For the rash and outrageous opinions ex-|
| Digital Equipment, Maynard MA     pressed herein I alone am responsible;  |
| ewanco@kalvin.enet.dec.com        they do not belong to DIGITAL(TM).      |
\==========================- 2 Th 2:15 -====================================/