Mail Archives: djgpp/1994/07/12/05:14:36

Date: Tue, 12 Jul 1994 10:51:18 +0200
From: terra AT diku DOT dk
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Cc: leisner AT sdsp DOT mc DOT xerox DOT com
Subject: Re: controlling where go32 puts program

   X-Mailer: exmh version 1.4 6/24/94
   Date: Mon, 11 Jul 1994 09:40:44 PDT
   From: Marty Leisner <leisner AT sdsp DOT mc DOT xerox DOT com>

   I want to recursivesly do makes...

   It seems each invocation takes over 100k out of my conventional memory,
   so after 3 levels I'm "out of space to exec"

The Gnuish make (and swalib) was mentioned.  The `problem' with 
these is that swalib is MicroSoft C specific and quite heavily
so.  Otherwise, I believe this to be a very good library -- it
swaps to XMS or disk.

My port of Gnu Make 3,71 ( out there) takes up around
30K at exec time.  If that's not good enough you should be able
to hack the swapping routine and get down to 1K + space for 
environment.  A couple of hours, max.  I just never needed it.
[Incidently, this swapping routine could easily be merged with
go32 if anybody wants to.]

The reason that Djgpp 2.0 will not have a memory-eating exec is
that there will be no go32.  The first invocation of a Djgpp
program will make sure that a Dpmi host is available.  The next
will just use it.  In other words, there is no need to blame
Qdpmi for eating memory.

Morten Welinder
terra AT diku DOT dk

- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019