Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 12 Jun 2002 01:29:10 -0400
From: Christopher Faylor <cgf-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Am I missing something?
Message-ID: <20020612052910.GA21519@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20020612002933.A10609@monster.rich-paul.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020612002933.A10609@monster.rich-paul.net>
User-Agent: Mutt/1.3.23.1i

On Wed, Jun 12, 2002 at 12:29:33AM -0400, linguist-cygwin@rich-paul.net wrote:
>I had to change wincap.{cc,h} in order to get the 6/9/2002 snapshot to
>work for me.  Without that, every cygwin program would segfault before
>entering main, due to trying to access wincapc in the pthreads
>initialization code.
>
>It seems odd, however, that there's been no discussion of such a
>problem on this list or the cygwin developer's list.

http://cygwin.com/ml/cygwin/2002-06/msg00528.html

>Thus my question: have I missed something?  Or am I the only one trying
>snapshots?
>
>Anyway, my patch is here, FWIW:

I appreciate the fact that you are trying snapshots but you really
should check that you are actually running the *latest* snapshot.

I also very much appreciate the fact that you're providing patches but,
for the patches to be useful, it's usually safer to generate them
against cvs.  If you're rebuilding cygwin, you'll see fixes much more
quickly if you update from cvs.

Anyway, in this case, the problem was discovered and fixed on
2002-06-10.

cgf
--
Please do not send me personal email with cygwin questions.
Use the resources at http://cygwin.com/ .

--
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/