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
Message-ID:	<00b201c0c0e0$5b948040$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	<cygwin-developers AT cygwin DOT com>
Subject:	Chris - a question for you
Date:	Mon, 9 Apr 2001 20:32:18 +1000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime:	09 Apr 2001 10:25:49.0868 (UTC) FILETIME=[729066C0:01C0C0DF]

Chris,
    Are mtsafe support and the ALLOW_PTH in cygwin.din linked? I ask
because of all the empty functions in the bottom of pthread.cc. It would
be nice to just zap that whole list and simply not export the functions
if cygwin is built non mt safe.

If they aren't linked (ie non mtsafe and ALLOW_PTH is a valid
combination today) can we link them and disable pthread function exports
when non-mtsafe?

Rob

- Raw text -