Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs Date: Thu, 18 May 2000 17:08:45 -0500 (CDT) From: Mumit Khan To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: Can't build the latest snapshot with gcc-2.95.2-1 In-Reply-To: <20000518173225.A17562@cygnus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 18 May 2000, Chris Faylor wrote: > Ok. I've moved it out. It's no big deal since it is always called once. > It almost sounds like there was a static buffer being set aside in every > file including sigproc.h, which I certainly don't want. > > In case anyone is curious about the strange muto construction, I have to > assign a static buffer because mutos are used prior to jumping into the > fork magic and they get confused when the heap changes after a fork > operation. > > One of these days DJ or I are going to clean up the winsup include file > layout. It is really frustrating to deal with... > > Sorry about not getting the problem on the first round. I'm actually > glad that I made the changes that I did to winsup, though. I think > it cleaned up some include file stuff. > > Please let me know if the changes I have now made fix the problem. > The problem is now gone, thanks. IMO it's worth all the little problems if it means that winsup.h is cleaned up! Regards, Mumit