Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Thu, 9 Mar 2000 23:16:34 -0500 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: winsup changes? Message-ID: <20000309231634.B6844@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: ; from matt@use.net on Thu, Mar 09, 2000 at 07:07:26PM -0800 On Thu, Mar 09, 2000 at 07:07:26PM -0800, Matt wrote: >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/reent.h, 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. I should point out that MAKE_MODE has nothing to do with header files... cgf