Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID: <3B92F0CF.4040101@ece.gatech.edu>
Date: Sun, 02 Sep 2001 22:54:07 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: cygwin-developers AT cygwin DOT com
Subject: Re: cygwin 1.3.3 announcment -- extra words solicited
References: <999380998 DOT 30841 DOT ezmlm AT sources DOT redhat DOT com> <3B92D324 DOT 9030308 AT ece DOT gatech DOT edu> <3B92EC8F DOT 3070605 AT ece DOT gatech DOT edu> <20010902224411 DOT A21914 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Christopher Faylor wrote:


> Yes, I've built a cygwin1.dll without error but I don't think I've
> bootstrapped it in the manner that you are describing.  I rarely check
> out anything via 'cvs checkout'.  I just use 'cvs update' to freshen
> my tree.


The key here is not how the local source tree was 'upped' to the latest 
version.  I only did a complete checkout b/c I got the error with 'cvs 
up' as well.  I hypothesized that the problem was due to my wacky guinea 
pig status w.r.t. inherited directory permissions -- "*Leaving 
directory* foobaz" ==> signal 11 -- so I wiped out my local source tree 
and recreated it from scratch via "cvs checkout".  This insured that all 
directories within my source tree had "good" permissions and whatnot.

But that was wrong.

Because after doing the complete checkout, I still saw the error.

> 
> I did a reconfigure and a 'make clean all' without error.


*while using a development kernel as your active cgywin1.dll* ?  Or just 
the released 1.3.2 kernel?

--Chuck