Date:	Fri, 18 Jun 93 13:59:57 EST
From:	carolo AT dcc DOT unicamp DOT br (Fernando P. Carolo Jr.)
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: Borland 3.1 make adn djgpp
Cc:	carolo AT dcc DOT unicamp DOT br

>From: Joe Clark <joe AT ziggy DOT larc DOT nasa DOT gov>
>To: djgpp AT sun DOT soe DOT clarkson DOT edu
>Subject: Borland 3.1 make and djgpp
>
>I have both Borland's make utility that came with
>Borland 3.1 and Turbo C's make that came with 1.01.
>When I use the Turbo C make everything works fine
>(although compiling time is about double using
>gcc vice tcc/bcc).  However when I use the newer make
>gcc starts to compile than seems to freeze altogether.
>If I catch it soon enough Ctrl-C will stop the process
>otherwise I have to reboot.  I also noticed that
>when using the older make I get a 400+Kbytes available message
>before every compilation step, and when I use the newer one 
>I get 4+Mbytes available.
>
>Is there a switch I have to use when compiling gcc programs
>under the newer versions of Borland's make?

  Borland make which cames with version 3.1 uses its internal DMPI host
(if no other one is avaiable), and I've seen djgpp's gcc to crash when
called from Borland's make.
  Happily, there's a solution: run the maker program that comes with
Borland C++ 3.1. It's a real mode make, who works like older versions,
and will report about 450-500k free memory. I hope this solve your problem.

------------------------------------------------------------------------------
| Fernando P. Carolo Jr.                                                     |
| Dept. of Computer Science - Univ. of Campinas - Campinas - SP - Brazil     |
| Internet: carolo AT dcc DOT unicamp DOT br                                            |
------------------------------------------------------------------------------

- Raw text -