Date: Sun, 3 Nov 1996 11:44:01 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "John M. Aldrich" <fighteer AT cs DOT com>
Cc: tehmul%NIITPUN AT iris DOT ernet DOT in, djgpp AT delorie DOT com
Subject: Re: v2.01 and v2.00 binaries.
In-Reply-To: <327C18E8.4DF0@cs.com>
Message-Id: <Pine.SUN.3.91.961103113832.27986M-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Sat, 2 Nov 1996, John M. Aldrich wrote:

> > I forgot to D/L gpp*.zip, the one which contains the C++ compiler.  I tried
> > using the V2.00 cc1plus.exe with the rest of the V2.01 kit and it seems to
> > work.  I've only tried it out on small test programs.  Will I face a problem
> > later?  Or should I just get wise and d/l that file as well?
> 
> The problem is that v2.00 programs don't recognize the method of passing
> long command lines that v2.01 programs use.  So any command line that
> make, gcc, etc., tries to pass to your v2.00 cc1plus can be no greater
> than 126 characters or it will fail.

Actually, most cases will work even with command lines longer than 126
characters, because they use `spawn' which passes command lines in the
same old !proxy way it did before v2.01.  Only `system' now uses the new
method, and Make only calls `system' for commands that use redirection,
wildcards and other shell features (gcc doesn't call `system' at all
AFAIK). 

However, I do urge people to upgrade and not mix v2.0 executables with
v2.01 ones, because when these problem do bite you, they are very subtle
and hard to debug.