From:	kunst AT prl DOT philips DOT nl
Subject:	Re: compiling go32.exe
To:	eichin AT cygnus DOT com (Mark W. Eichin)
Date:	Tue, 13 Oct 92 10:59:37 MET
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Mailer:	Elm [revision: 70.30]

> 
> I've been trying to build go32... since it needs a 16-bit compiler, I
> went and got Turbo C++ 3.0, which had Turbo C. That seems to compile
> the .c files with only a few warnings (once adding -P-c to CFLAGS) but
> then I discovered that the package doesn't include the Turbo
> Assembler. (I haven't yet figured out where to get that -- there are
> references to it being part of some Borland "professional" package in
> some ads, but I haven't seen anything in the catalogs I've got, in
> particular there's nothing in the literature that came with Turbo
> C++...)
> 	I've tried several assemblers (Microsoft MASM 1.25 and several
> freeware assemblers off of simtel20) and all of them seem to have
> problems with the "segment" directives as used in the start_data16 and
> similar macros. Is there any other assembler that will work as/is? If not,
> has anyone ported these macros, or at least has a description of what
> they really mean and how to change them for other assemblers?

I think DJ uses Turbo C 2.0 for compiling go32.
I successfully compiled go32 using both Borland C++ 2.0 and 3.0,
although 'some' additional error messages are given with these compilers.
Try to get one of these. They include an assembler as well.

Pieter Kunst (kunst AT prl DOT philips DOT nl)
Software help desk person: 'No sir, it's not a bug, it's a feature !'

- Raw text -