From: dslate AT interaccess DOT com ("David J. Slate")
Subject: gnu-win32 gcc compiler error
8 Sep 1997 20:26:46 -0700
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199709080911.EAA31195.cygnus.gnu-win32@pc4.prs.nunet.net>
Original-To: dslate AT interaccess DOT com, gnu-win32 AT cygnus DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Subject: gnu-win32 gcc compiler error
Reply-To: dslate AT interaccess DOT com
To: gnu-win32 AT cygnus DOT com

I am using the gnu-win32 package under both Windows-95 and Windows-NT, and
so far it is working pretty well, but one strange (but perhaps harmless)
quirk is that gcc seems to get an internal compiler when it detects syntax
errors.  For example, the following script:

	#!/bin/sh -x
	# Demonstrate gcc abort on syntax errors under gnu-win32.

	date
	uname -a
	echo
	cat gccabt.c
	echo
	gcc gccabt.c
	date

produces on stdout:

	Mon Sep  8 08:32:10 GMT-6:00 1997
	CYGWIN32/95 DEFAULT 4.0 17.5 i6366486

	int
	main( int argc, char *argv[])
	{
		blah
	}

	Mon Sep  8 08:32:11 GMT-6:00 1997

and on stderr:

	+ date
	+ uname -a
	+ echo
	+ cat gccabt.c
	+ echo
	+ gcc gccabt.c
	gccabt.c: In function `main':
	gccabt.c:5: `blah' undeclared (first use this function)
	gccabt.c:5: (Each undeclared identifier is reported only once
	gccabt.c:5: for each function it appears in.)
	gccabt.c:5: syntax error before `}'
	gcc: Internal compiler error: program cc1 got fatal signal 33
	+ date

Does anyone have any ideas on what is causing this?

Thanks,

-- Dave Slate
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".