Re: Help with GNUMAKE on PC platform - command line lenghtlimitations

[address@hidden]

If running in a DOS shell,
Increase environment space.

all command line text is stored in an environment string.
If the environment space is too small (say 2048 bytes) then
the make can easily overflow the space with a very very long
command line.  say a compile command that has many complete
paths to include files and the like.

Increasing the environment space is only temporary fix.
eventually you will hit the limit and make will fail in
an unknown but repeatable way.

The failure is not apparent since the make commands may be hidden
in a bash or csh unix shell emulator running on win32 platform.

Real answer is to use true bash, csh etc. unix shell
or switch to winXP

address@hidden

----- Original Message ----- 
From: "Eli Zaretskii" <address@hidden>
To: <address@hidden>
Cc: <address@hidden>
Sent: Tuesday, July 29, 2003 5:17pm
Subject: Re: Help with GNUMAKE on PC platform - command line
lenghtlimitations


> Date: Tue, 29 Jul 2003 14:05:29 -0500
> From: "Ron.E.Gaskins" <address@hidden>
>
> I am switching from OPUSMAKE to GNUMAKE on a PC platform.  I would like
assistance/advice on the following:
>
> FILES= file1 file2 file3 file4 .... File99
> Clean: erase $(FILES)
>
>
> This causes problems on a PC because of the length of the erase command
exceeds the limits.

What limit is that, and which port of GNU Make do you use?

In general, unless you mix incompatible toolchains, the limitation on
command-line length should be very far away, like 16KB or so.  This
should be more than enough for very long command lines.


_______________________________________________
Make-w32 mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/make-w32