Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-Id: <4.3.1.2.20000928061029.02114e10@pop.ma.ultranet.com>
Date: Thu, 28 Sep 2000 06:14:05 -0400
To: david@carter.net, libwww@perl.org;, cygwin@cygwin.com
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
Subject: Re: HTML-Parser-3.25 fails t/filter.1 on cygwin
In-Reply-To: <20010530154504.15784.cpmta@c000.snv.cp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 11:45 AM 5/30/2001, david@carter.net wrote:
>Debugging the HTML::Parser test above showed that the in-memory string $HTML contained only ascii 10's at line-end, while the string read back from disk ($FILTERED) had the 13/10 combination.
>
>Cygwin list - any ideas? I've installed previous versions of HTML::Parser with no problems. I upgraded to the most recent released version of cygwin yesterday.
>
>$ uname -a
>CYGWIN_NT-5.0 DCARTER 1.3.2(0.39/3/2) 2001-05-20 23:28 i686 unknown
>
>$ mount
>d:\cygwin\bin on /usr/bin type system (textmode)
>d:\cygwin\lib on /usr/lib type system (textmode)
>d:\cygwin on / type system (textmode)
>c: on /cygdrive/c type user (textmode,noumount)
>d: on /cygdrive/d type user (textmode,noumount)
>e: on /cygdrive/e type user (textmode,noumount)


Did your mounts change in the recent install?  From what you've shown here,
every file created will be text format.  textmode is not the typical mount
type for the first three mount points you show.  If you had these mount 
points as binmode before, this may account for some of the problems you 
see now.  Do you know if HTML::Parser is properly ported to systems where
behavior of files in textmode != binmode?


Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple