Date: Wed, 3 Jan 2001 10:56:16 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Laurynas Biveinis <lauras AT softhome DOT net>
cc: DJGPP Workers <djgpp-workers AT delorie DOT com>
Subject: Re: Stability of new long arg passing code?
In-Reply-To: <3A522D5A.C51044D0@softhome.net>
Message-ID: <Pine.SUN.3.91.1010103105453.1129N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 2 Jan 2001, Laurynas Biveinis wrote:

> I'm experiencing strange problems with GCC, compiled with current
> djdev CVS. The compiler randomly aborts with error messages like
> cc1.exe: Unrecognized option `-c'

Is it certain that the library is the cause?  In other words, can you
build GCC with stock v2.03 library and see that this problem doesn't
happen there?

> (Replace `-c' with any valid GCC option). When I restart
> make, it might compile a few more files and stops again.

When did that start happening?  If it started recently, and if stock
v2.03 libc doesn't have this problem, one possible cause might be the
changes I committed for supporting CMDLINE on Windows.  You don't explain 
why you think that is the case, as the Subject says.

One possible way to debug this is to add some debugging print-outs in
the functions which issues this "Unrecognized option" message, and see
what kind of data in there gets corrupted.

What do you have for a shell when you see these problems?