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 sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Tue, 10 Apr 2001 23:49:19 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: cygwin with --disable-threadsafe Message-ID: <20010410234919.A25082@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from robert.collins@itdomain.com.au on Wed, Apr 11, 2001 at 11:06:42AM +1000 On Wed, Apr 11, 2001 at 11:06:42AM +1000, Robert Collins wrote: >Following up on my questions about @PTH_ALLOW@ I tried build cygwin with >--disable-threadsafe. It didn't build - pinfo and signal.h appeared to >be the main culprits. > >Have I broken something with my changes (I haven't removed the stub >functions that are under discussion yet), or is it currently broken? And >yes I plan to test it, but I may have something wrong here so an outside >reference point is useful. It looks like Cygwin doesn't even build with --disable-threadsafe anymore. I don't think this is a big deal and I doubt that it has anything to do with your changes. I guess I should just get rid of the option entirely. So, we can forget about the PTH_ALLOW kludge. Sorry for not realizing this sooner. cgf