Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Wed, 15 Mar 2000 00:46:53 -0500
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Permission denied with makeinfo from texinfo-4.0
Message-ID: <20000315004653.A4933@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: cgf AT cygnus DOT com, cygwin AT sourceware DOT cygnus DOT com
References: <200003150435 DOT XAA12288 AT mail DOT bcpl DOT net>; <20000315000856 DOT C3982 AT cygnus DOT com> <200003150530 DOT AAA24404 AT mail DOT bcpl DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.8i
In-Reply-To: <200003150530.AAA24404@mail.bcpl.net>; from dbryan@bcpl.net on Wed, Mar 15, 2000 at 12:30:41AM -0500

On Wed, Mar 15, 2000 at 12:30:41AM -0500, J. David Bryan wrote:
>On 15 Mar 2000, at 0:08, Chris Faylor wrote:
>
>> Defining -DWIN32 is not usually a good idea.  It usually causes packages
>> to use windows specific code and workarounds which are not necessary for
>> cygwin. 
>
>Generally sound advice.  However, in this case, -DWIN32 changes the 
>behavior of only file (files.c) of the makeinfo source.  It does two 
>things:
>
> * It works around the bug mentioned, albeit by reading the source file a
>   character at a time instead of all in one go.

I don't know why reading the file a character at a time would do anything
but slow down texinfo.  Don't you still get a \r and a \n?

> * It does not use $HOME as a search path for texinfo files.

Why is this desirable?

>To avoid the problem, O_BINARY must be undefined, not simply zero.  
>Undefining it will avoid the invalid buffer (by compiling different code) 
>at the cost of losing the ability to process texinfo files containing 
>Windows line ends.

So this was just a problem with \r\n in a texinfo file?  The solution to
that seems simple enough.

Patient: "Doctor, it hurts when I do this."
Doctor: "Hmm.  Maybe you need an x-ray."

or something like that.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com