From:	kunst AT prl DOT philips DOT nl
Subject:	re: compiling go32.exe
To:	eichin AT cygnus DOT com (Mark W. Eichin)
Date:	Thu, 15 Oct 92 9:00:23 MET
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Mailer:	Elm [revision: 70.30]

> 
> Well, I've gotten all of the .c files (at least under go32/) to
> compiler with Turbo C 3.0 (made one change: the printf implementation
> in mono.c uses &... to pass the ... argument to vsprintf; tcc
> complained that it wasn't an lvalue, but changing it to pass ...
> directly at least compiled. I'll see later if it worked.)

Borland C++ 2.0 and 3.0 need this patch too, I remember again...

> 	I've also gotten most of the .asm files to build with MASM
> 5.1, but not all - MSWITCH.ASM uses the construct "extrn _gdt:gdt_s"
> which masm won't deal with (gdt_s is a "struct" and masm only seems to
> deal with builtin types there, such as "word", "byte", and "near".) I
> think I can get around this by using "extrn _gdt:byte" instead, and
> then replacing things like "and _gdt[g_ptss].stype,0FDh" with
> something like 
> 	gdt_s_size equ size gdt_s; 
> 	and _gdt[g_ptss*gdt_s_size].stype,0FDh
> 
> Does this sound like it makes sense? 

I think you could save yourself a lot of time by obtaining a copy
of Turbo Assembler (tasm) somewhere instead !

> (I've at least gotten the whole
> thing to build; go32t hangs almost immediately, and debug32 gets as
> far as putting up some colored text before rebooting the machine. I'll
> keep looking at those changes to mswitch...)

Using tasm will result in a running version of GO32 with no changes...

Pieter Kunst.

- Raw text -