Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3BBD3E80.8090101@ece.gatech.edu>
Date: Fri, 05 Oct 2001 01:00:48 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: REALLY need help prior to 1.3.4 release
References: <20011003000916 DOT A28775 AT redhat DOT com> <3BBAA8EC DOT 3000706 AT ece DOT gatech DOT edu> <20011003110421 DOT E28936 AT redhat DOT com> <20011003112140 DOT J28936 AT redhat DOT com> <20011003225215 DOT A23380 AT redhat DOT com> <3BBC63AB DOT 1070203 AT ece DOT gatech DOT edu> <20011004224133 DOT A19253 AT redhat DOT com> <3BBD2F1E DOT 3060204 AT ece DOT gatech DOT edu> <20011005000952 DOT A5265 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


>>>>I updated to "current" CVS last night around 1am EDT, and rebuilt 
>>>>cygwin.  After installing that, I saw the same behavior as before: raw 
>>>>read worked, raw write did not (Permission denied).  :-(
>>>>
>>>>
>>>This was really strange.  Everything worked fine for me until I ejected
>>>my floppy.  From that point on, I couldn't write to any floppy.  I had to
>>>scroll back several times to convince myself that I wasn't
>>>hallucinating.
>>>
>>>Anyway, since I could eventually duplicate the problem, I could actually
>>>fix it.
>>>
>>>So, how about *now*, Chuck?  Does it work *now*?


Yes, it works now.  raw read.  raw write.  eject.  insert.  raw write. 
All works fine.

>>
>>Per the earlier discussion about autoconf-2.13/2.52, I was attempting to 
>>do a side-by-side installation of the two, and decided to run the 
>>checks.  (eventaully to write a script that parses configure.in for the 
>>AC_REQ[] line to determine which one to call, etc).
>>
>>2.13 had "226 expected passes, 33 unexpected failures".  (On both 
>>cygwin-20011001, and cygwin-1.3.3-2).  This is the same as our previous 
>>experiments, if you remember those.
>>
>>2.52 was failing all over the place with cygwin-20011001.  (With 1.3.2, 
>>we had finally gotten autoconf to pass all tests).  I'm currently 
>>running the tests again with 1.3.3-2, to make sure the 'breakage' 
>>occurred during the 1.3.4 development cycle and not before.  So far I'm 
>>passing all tests with 1.3.3-2 (but this'll take several more hours to 
>>complete on my machine).
>>
> 
> There have been a considerable number of changes since 2001/10/01.  I
> didn't ask for volunteers to check this out until 10/3.  That is when I
> ostensibly finished all of my infrastructure changes.
> 
> I wouldn't have expected that things would actually be broken on
> 2001/10/01 but it certainly makes sense to use a newer snapshot (or,
> even better, CVS) if possible.


Okay, I'm re-running the tests now, under my fresh-from-the-oven 
cgywin1-20011005.  We'll see what the results are tomorrow morning.

--Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/