From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11719 invoked by alias); 21 Jan 2008 13:02:14 -0000 Received: (qmail 11703 invoked by uid 22791); 21 Jan 2008 13:02:13 -0000 X-Spam-Check-By: sourceware.org Received: from lts-mxgateway.goodrich.com (HELO lts-mxgateway.goodrich.com) (12.129.98.97) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 21 Jan 2008 13:01:45 +0000 X-AuditID: ac15863a-ad8c7bb00000554c-52-479497b7ed50 Received: from GR-GWI-WEST-A.goodrich.com (gr-gwi-west-a.goodrich.com [170.126.245.4]) by lts-mxgateway.goodrich.com (Symantec Mail Security) with ESMTP id 8BFEC4DC003; Mon, 21 Jan 2008 08:01:43 -0500 (EST) Received: from nhc1ex01.goodrich.root.local (localhost [127.0.0.1]) by GR-GWI-WEST-A.goodrich.com (8.13.5/8.13.5) with ESMTP id m0LD18Nq020541; Mon, 21 Jan 2008 08:01:18 -0500 (EST) Received: from nhc0ex13.goodrich.root.local ([170.126.245.54]) by nhc1ex01.goodrich.root.local with Microsoft SMTPSVC(6.0.3790.1830); Mon, 21 Jan 2008 08:01:02 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: use of pthreads-win32 in gnulib? Date: Mon, 21 Jan 2008 13:02:00 -0000 Message-ID: <35737E0536AA3D4BA26F10F103C8ABF808062021@nhc0ex13.goodrich.root.local> In-Reply-To: <200801190227.10706.bruno@clisp.org> References: <200801190227.10706.bruno@clisp.org> From: "Burkhardt, Glenn" To: "Bruno Haible" , Cc: X-IsSubscribed: yes Mailing-List: contact pthreads-win32-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sourceware.org X-SW-Source: 2008/txt/msg00002.txt.bz2 We have an application on MinGW that uses pthreads-win32, and I haven't had any problems. I did need to pick up a Posix timer package as well for our application, since MinGW doesn't have one. I used the now obsolete LinuxThreads timers, which make use of pthreads, and it works without problems for us. It would be nice if pthreads-win32 would pick this up, since timers are probably almost always needed if threads are needed.=20 > -----Original Message----- > From: pthreads-win32-owner@sourceware.org=20 > [mailto:pthreads-win32-owner@sourceware.org] On Behalf Of Bruno Haible > Sent: Friday, January 18, 2008 8:27 PM > To: pthreads-win32@sourceware.org > Cc: bug-gnulib@gnu.org > Subject: use of pthreads-win32 in gnulib? >=20 > Hi, >=20 > The GNU gnulib project [1][2] provides a portability library=20 > for porting programs written against the POSIX API to all=20 > kinds of platforms. One of these platforms is mingw (native=20 > Win32 API). >=20 > All reasonable porting targets nowadays implement the POSIX=20 > threads API, except for mingw. (The others that don't are=20 > Solaris 2.4 and BeOS. But these are not reasonable porting=20 > targets any more.) Therefore your library would nicely fit=20 > into gnulib. >=20 > What gnulib provides so far, relating to multithreading, is=20 > only a portable layer for handling locks (mutexes) and TLS.=20 > But generally it's preferrable to use the POSIX API rather=20 > than some other API; this is another reason why your library=20 > is interesting for gnulib. >=20 > How well tested is pthreads-win32? Is there a list of=20 > packages that uses it? >=20 > Can it be built on mingw with pretty clean, standard Makefile=20 > infrastructure? > Does building with "gcc -Wall" produce only a small amount of=20 > warnings? >=20 > If gnulib started to "virtually" include your library (i.e.=20 > make it available in source code when a gnulib user requests=20 > the gnulib module 'pthreads'), would that be OK with you? >=20 > Regards, > Bruno >=20 >=20 > [1] http://www.gnu.org/software/gnulib/ > [2] http://savannah.gnu.org/projects/gnulib >=20 >=20