Date:	Thu, 25 Nov 1999 10:06:18 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Prashant TR <prashant_news AT yahoo DOT com>
cc:	DJGPP Mailing list <djgpp AT delorie DOT com>
Subject:	Re: Running Borland compiler from GNU Make
In-Reply-To:	<001601bf36ed$f74e0de0$30f838ca@home-computer>
Message-ID:	<Pine.SUN.3.91.991125100605.11831K-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 25 Nov 1999, Prashant TR wrote:

> >"Stephen Roderick" <stephen_roderick AT ssl DOT umd DOT edu> wrote in message
> >news:383C2C21 DOT 4586642A AT ssl DOT umd DOT edu...
> >> Using gnu make to run bcc.exe (Borland's 16-bit compiler) under
> >> DOS (Winddoze 95 DOS) provides a nice descriptive error of
>
> If you have 32rtm (I'm using BC 5), run this before you run the GNU
> Make. The culprit here seems to be CWSDPMI. With 32rtm,
> everything works fine.

The original problem happens on Windows 95 (see above), so CWSDPMI has
nothing to do with it.

You simply CANNOT run 16-bit and 32-bit DPMI programs in the same VM.
If 32rtm allows this (I doubt it), it certainly uses some inside
knowledge of Borland's DPMI server/client internals.

- Raw text -