Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From:	Matt <matt AT use DOT net>
X-Sender:	matt AT cesium DOT clock DOT org
To:	cygwin-developers AT sourceware DOT cygnus DOT com
Subject:	Re: winsup changes?
In-Reply-To:	<Pine.NEB.4.10.10003091617480.28368-100000@cesium.clock.org>
Message-ID:	<Pine.NEB.4.10.10003091902200.28368-100000@cesium.clock.org>
MIME-Version:	1.0
Date:	Thu, 9 Mar 2000 19:07:26 -0800

On Thu, 9 Mar 2000, Matt wrote:

> I just installed the 3/4 cygwin-inst package, and tried to build bison
> with it. My MAKE_MODE is set to UNIX, but the several of the header files
> in i686-pc-cygwin/include (stdio.h, sys/ree, etc) generate loads of
> "stray '\' in program" errors, and in turn other parsing errors.
> 
> Since cygwin defaults to MAKE_MODE=UNIX, should those stray backslashes be
> in the files by default? Am I just missing something?

Ok, I figured it out. I use WinZip to extract cygwin inst and DLL packages
since using cygwin tools themselves would prevent them from being updated.
After using winzip to uncompress the cygwin-inst package, and then
uncompressing again in bash, all the header files worked fine.

wwweeeird.

Sorry for any confusion.


--
it's only fair to tell you
I'm absolutely cuckoo

- Raw text -