Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Thu, 18 May 2000 17:32:26 -0400
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: Can't build the latest snapshot with gcc-2.95.2-1
Message-ID: <20000518173225.A17562@cygnus.com>
Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com
Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com
References: <s1sln17hcid DOT fsf AT jaist DOT ac DOT jp> <Pine DOT HPP DOT 3 DOT 96 DOT 1000518160133 DOT 20231G-100000 AT hp2 DOT xraylith DOT wisc DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.12i
In-Reply-To: <Pine.HPP.3.96.1000518160133.20231G-100000@hp2.xraylith.wisc.edu>; from khan@NanoTech.Wisc.EDU on Thu, May 18, 2000 at 04:16:14PM -0500

On Thu, May 18, 2000 at 04:16:14PM -0500, Mumit Khan wrote:
>$ i686-pc-cygwin-gcc -g -O2 -fno-exceptions -fno-rtti -c bug.cc
>$ i686-pc-cygwin-nm --dem bug.o | grep muto
>         U muto::~muto(void)
>
>Argh.
>
>The only solution I see now is to move the sigthread::init method to
>an implementation file as an out-of-line definition instead.

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.

cgf