gap-forum@samson.math.rwth-aachen.de
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
gcc -c tietze.c gcc -c string.c gcc -c set.c gcc -c statemen.c
gcc -c record.c gcc -c scanner.c gcc -c rational.c gcc -c read.c
gcc -c polynom.c gcc -c range.c gcc -c permutat.c gcc -c plist.c
gcc -c pcpresen.c gcc -c list.c gcc -c integer.c gcc -c gasman.c
gcc -c idents.c gcc -c function.c gcc -c finfield.c gcc -c cyclotom.c
gcc -c eval.c gcc -c blister.c gcc -c costab.c gcc -c aggroup.c
gcc -c agcollec.c
(3) compile the main program (also system independant)
gcc -c gap.c
(4) archive the object files of all subroutines into a "gaplib.a" archive
ar -cr gaplib.a sysdos.o ar -cr gaplib.a set.o
ar -cr gaplib.a word.o ar -cr gaplib.a agcollec.o
ar -cr gaplib.a aggroup.o ar -cr gaplib.a costab.o
ar -cr gaplib.a blister.o ar -cr gaplib.a eval.o
ar -cr gaplib.a cyclotom.o ar -cr gaplib.a finfield.o
ar -cr gaplib.a function.o ar -cr gaplib.a idents.o
ar -cr gaplib.a gasman.o ar -cr gaplib.a integer.o
ar -cr gaplib.a list.o ar -cr gaplib.a pcpresen.o
ar -cr gaplib.a plist.o ar -cr gaplib.a permutat.o
ar -cr gaplib.a range.o ar -cr gaplib.a polynom.o
ar -cr gaplib.a read.o ar -cr gaplib.a rational.o
ar -cr gaplib.a scanner.o ar -cr gaplib.a record.o
ar -cr gaplib.a statemen.o ar -cr gaplib.a string.o
ar -cr gaplib.a tietze.o ar -cr gaplib.a unknown.o
ar -cr gaplib.a vector.o ar -cr gaplib.a vecffe.o
ranlib gaplib.a
(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!

Jacob Hirbawi
JcbHrb@CERF.net