Date:	Thu, 21 Sep 95 14:09:54 +0200
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
From:	til AT zentrum DOT phys DOT chemie DOT tu-muenchen DOT de (Tilmann Haeberle)
Subject:	Summary: Command Lines>2000 bytes?

My questions were: 
1) Is there any possibility to pass longer command lines than
   (4K - environment_size) to gcc?
2) Or is there any possibility to increase the transfer buffer size?
3) The makefile worked under 1.11 - Maybe the problem is related to a difference
    between 1.11 and 1.12?


The answer to 1) and 2) is no, 3) yes.

Workaround 1) and 2) (Eli Zarteskii)
--------------------
Since my command-line length is just on the borderline 
of what DJGPP can handle, the environment can be reduced 
by invoking an inferior COMMAND.COM (without /e:), there only 
the used part of the environment uses space.

I use now the following command for starting compilation (in a batch file)

        command /C make -f myprog.mak myprog.exe

Comment to 3) (Charles Sandmann)
-------------
Yes, this behavior was changed for V1.12, and it has caused some problems.  
... Since GO32 is a dead program (goes away in V2) there is no incentive 
to fix it.

> How will this be handled under V2.0?

All of this manipulation is done in 32-bit mode in V2, so the space is
just malloc'ed out of the 32-bit pool of memory.  When exec'ing another
32-bit program, I don't remember exactly how it works, but the transfer
buffer is 16Kb in V2, so even if they did mess it up (doubtful...) there
would be much less of a problem.

Another tip (John Carter)
-----------
Using ar to keep the number of files smaller. (But not generally usable)
______________________________________________________________________
Tilmann Haeberle        e-mail: til AT zentrum DOT phys DOT chemie DOT tu-muenchen DOT de
Institut fuer physikalische Chemie I  Tel: 089/3209-3373
TU Muenchen 
Lichtenbergstr. 4                     Fax: 089/3209-3026    
D-85747 Garching, Germany

- Raw text -