🚀 go-pugleaf

In article <1602@tellab5.tellabs.CHI.IL.US> gad@tellab5.UUCP (Greg Deuerling) writes:
<I compile with "lc -L test.c", and I use UNHUNK as "unhunk -p test test.out".
<UNHUNK generates the following :
<
[deleted]
<1 errors encountered

Lattice has extended the hunk types, and convinced CBM to make them
part of the standard for the Amiga (at least, that's the way I hear
it). UnHunk predates all of this, and so doesn't understand the new
types.

One option would be to call Lattice to get the new hunk definitions,
and add them to UnHunk. You might also try compiling with -Lt instead
of -L, to force one code hunk & one data hunk.

<Why is the output so long, I would think that test.c would be less than 
<100 bytes (I compiled the same test.c with UNI-WARE on a VAX and the output
<was around 45 bytes).

Because Lattice is providing lots of support software you probably
don't want in this case (but generally do): argument parsing, memory
cleanup, opening a window for stdio to point to, and other stuff.
Renaming main as _main will take care of most of it. You can also link
with the apropriate magic option to make references to __main resolve
to _main - check the library documentation, under tinymain (or is it
_tinymain?).

<Are there any books or manuals sold that would give me the information
<to write a program that would strip out all of the scatter loading 
<stuff ???

I'm not sure what you mean by "strip out the scatterloading stuff."
You might look at the Lattice manuals for blink & lc; they tell you
how to get things down to a single hunk.

	<mike
--
Here's a song about absolutely nothing.			Mike Meyer
It's not about me, not about anyone else,		mwm@berkeley.edu
Not about love, not about being young.			ucbvax!mwm
Not about anything else, either.			mwm@ucbjade.BITNET