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
Subject: RE: cygwin with --disable-threadsafe
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
Date: Wed, 11 Apr 2001 14:08:57 +1000
Message-ID: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08EEE4@itdomain002.itdomain.net.au>
Thread-Topic: cygwin with --disable-threadsafe
Thread-Index: AcDCPD2TtuiqPKsXThCmgWshklZ4igAAMWxg
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-developers AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id AAA19784


> -----Original Message-----
> From: Christopher Faylor [mailto:cgf AT redhat DOT com]
> Sent: Wednesday, April 11, 2001 1:49 PM
> To: cygwin-developers AT cygwin DOT com
> Subject: Re: cygwin with --disable-threadsafe
> 
> 
> 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.

Should I remove that kludge and the #ifdef MT_SAFE stuff at the same
time? 

> Sorry for not realizing this sooner.

No Worries. It's not like pthreads has been under active development :]
 
> cgf
>