delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:4170 |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: 'make' problem |
Date: | Tue, 21 May 1996 13:16:09 CDT |
Organization: | Rice University, Houston, Texas |
Lines: | 11 |
Message-ID: | <31a20869.sandmann@clio.rice.edu> |
References: | <Pine DOT SUN DOT 3 DOT 91 DOT 960521140818 DOT 14153A-100000 AT is> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
NNTP-Posting-Host: | clio.rice.edu |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
> Borland Make (at least the revisions of BC I use) is a 16-bit DPMI > program, and it can never work with GCC. 16-bit and 32-bit DPMI clients > cannot be mixed at all. Beta 3 couldn't have supported this because this > is a fundamental limitation of the DPMI spec. Well ... it might work - and here's how ... Borland make loads it's own 16-bit dpmi server under DOS. When the V2 stub sees this, it tries to load CWSDPMI on top of the other DPMI provider. If this is sucessful, the V2 image can run under the Borland make (but only under DOS, NOT under Win). I'm not exactly sure why this would cause a floating error.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |