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: Mon, 9 Apr 2001 11:48:11 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: Chris - a question for you Message-ID: <20010409114811.D29051@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <00b201c0c0e0$5b948040$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <00b201c0c0e0$5b948040$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Mon, Apr 09, 2001 at 08:32:18PM +1000 On Mon, Apr 09, 2001 at 08:32:18PM +1000, Robert Collins wrote: >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? Experiment with turning on/off thread support. PTH_ALLOW puts a comment in front of the functions when threading is turned off. cgf