[comp.os.minix] Crosscompiling with Turbo-C

laverman@cs.rug.nl (Bert Laverman) (10/19/90)

  I wonder if some kind soul could MAIL me his/her experiences with Turbo-C
for crosscompiling, preferebly re Minix 1.5(.10(.3)). I understand Minix-PC
users have this alternative. The Minix-ST ACK compiler is not bad, but not
extremely good either; Kermit 5A(158) (the new beta-test version) compiles
to some 350Kb when including HELP and Interactive Command Processor. This
causes big problems, as kermit is the well-known exception to the rule that
a fork(2) is usually followed by an exec(2). (You do know that Minix-ST uses
shadowing, don't you? Now then, picture Minix trying to swap >350Kb each
time parent and child are switched. ;-)

  Anyway, a German firm called Heimsoeth gave us Turbo-C for the ST, so I started
wondering. Gcc is nice if you have 2Mb or more of memory (probably 4Mb makes it
pretty workable). C68k (thanks for the posting of the new binary  Christoph)
looks nice, but I haven't found out yet how to use it. Crosscompiling with
gcc on a Sun seems another option, but the diffs for the compiler are re 1.36,
and now everybody only has 1.37 sources!

[sorry for this intermezzo. back to the questions]
  I've been told Minix ST 1.5(.10.3) allows seperate I&D, just like Minix-PC.
This seems like another step towards solving the Kermit problem. Anybody have
experience with this? The ACK ld doesn't know about it. Can I just twiddle some
bits in the executable's magic number, or what?

  Any help and/or hints on the above mentioned questions would be appreciated.
I'ld prefer answers by email. If something interesting turns up, I'll report.

	Bert Laverman
	laverman@cs.rug.nl

==================================================================================
| For the Dutch speaking community:      | Bert Laverman, Dept. of Computer Sc.  |
|       AIO: Argeloze In Onderbetaling   | National University of Groningen, Nl  |
==================================================================================