Jacob Hirbawi writes in his e-mail message of 1993/03/08
In regards to my question last week about compiling gap under DOS;
first the bad news: I could not resolve the problems I was having with the
'make' utility in spite of the help I received from Martin. The good news is
that I managed to produce an executable by other means -- not as nice as using
the standard Makefile but at least I got this to work:

(1) compile the DOS specific subroutine
gcc -c sysdos.c -DSYS_IS_MSDOS
(2) compile the system independant subroutines
gcc -c vecffe.c gcc -c word.c gcc -c vector.c gcc -c unknown.c
[similar commands for the other source files]
(5) produce the executable and add the DOS extender part
gcc -o mygap gap.o gaplib.a -lpc
aout2exe mygap

The final result is mygap.exe which should be the functional equivalent of
the standard gap.exe. This is probably more detail than most would care to
know but hopefully this will be of some help since these commands can be
collected into one batch file without worrying about command line length
restrictions and the like; The executable seems to be working fine. Now I
have to figure out why it is a full 150KByes bigger than the standard gap.exe!

I think the reason that your executable is larger than ours is that we
use the optimizing option '-O2' of 'gcc'. This tends to decrease the
size of the executable (and it makes the executable faster too).

If you do this your executable should even be a little bit smaller than
ours, because we prepend the whole DOS extender to the executable while
'aout2exe' only adds a stub that loads the DOS extender at run time.

Martin.

-- .- .-. - .. -.  .-.. --- ...- . ...  .- -. -. .. -.- .-
Martin Sch"onert,   Martin.Schoenert@Math.RWTH-Aachen.DE,  +49 241 804551
Lehrstuhl D f"ur Mathematik, Templergraben 64, RWTH, D 51 Aachen, Germany