Mail Archives: djgpp/1996/08/26/01:26:52
On 25 Aug 1996, Julian LUIS Brown-Cardarelli wrote:
> Okie, I'm a long time borland programmer who is just making his
> move to DJGPP.. I was frightened to discover a problem during
> compilation that goes something like "cannot compile 16 bit apps."
I suspect the message that you saw was this:
"Can't handle 16 bit apps, sorry!"
If that's true, then the reason is that you have some of the Borland tools
installed on your machine, and they appear on your PATH before the DJGPP
bin/ directory. The usual problem is with cpp.exe (the pre-processor)
that's called the same in both packages. GCC tries to invoke the
Borland's cpp during the compilation, but Borland's tools are 16-bit DPMI
clients whereas DJGPP programs are 32-bit DPMI clients, and they cannot
be mixed (that's a limitation of DPMI 0.9 spec).
Solution? Assuming you really want to keep BC, just rename the Borland's
cpp.exe to something else, e.g. bcpp.exe. AFAIK, bc.exe and bcc.exe
don't need cpp unless you invoke cpp manually (the compilers have a
built-in pre-processor), so you shouldn't have any problems using both
DJGPP and BC. Another possibility is to change the order of your PATH;
actually, the latter possibility is even better, since the Borland's Make
program will also get you in similar trouble down the road.
> compilation that goes something like "cannot compile 16 bit apps."
^^^^^^^^^^^^^^^
In the future, please post the *exact* text of error messages you get.
Remote debugging problems of other people is hard enough as it is;
guessing what the original message was on top of that just might make it
mission impossible.
- Raw text -