[comp.os.minix] Re^2: C compilers and large code/data...

cechew@bruce.cc.monash.oz (Earl Chew) (03/13/90)

cagney@chook.ua.oz (Andrew Cagney - aka Noid,285,5585,3362395) writes:

>	1. You need to convert the minix assembler to MS or Turbo assembler
>	   (s2asm posted late last year worked for 1.4a, Mullen posted the
>	    assembler for 1.3).

s2asm addresses most of the problems associated with this.

>	2. Linking can be very hard, the file needs to be just right
>	   for it to be accepted by build and then work. How much do you
>	   know about segments and magic numbers...

This is the most confusing part. Basically what is required is to convert
the .exe file to a .out file. dos2out does this --- in a fashion. The one
posted with mcc does a better job.

>	3. You need to copy the files from minix to dos.

This is a small hassle --- a little script will do the trick. I think
that I gave up at one stage and decided to port ar.

>	4. For minix 1.5.x you need a different version of cpp to that
>	   supplied by Borland (If you are using TurboC). 
>	   The assembler files are run through cpp.

This is tricky. You *will* need a less brain damaged cpp. Perhaps Noid or I
should post the one we were using.

>	5. You need to rewrite the make files.

This is true --- but not that painful.

>	1. You loose MINIX's native compilation environment. If you
>	   like :-) unix this is a KILLER! Remember the make files...

The situation is not too bad if you have something like the MKS environment to
play in.

>	2. It is harder to do upgrades under dos. Remember the patches...

I don't believe that this is the case. I have ported patch to MessyDos. It
works fine.

Earl
-- 
Earl Chew, Dept of Computer Science, Monash University, Australia 3168
ARPA: cechew%bruce.cs.monash.oz.au@uunet.uu.net  ACS : cechew@bruce.oz
----------------------------------------------------------------------