From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8285 invoked by alias); 20 Jun 2008 11:45:22 -0000 Received: (qmail 8275 invoked by uid 22791); 20 Jun 2008 11:45:22 -0000 X-Spam-Check-By: sourceware.org Received: from phx-mxgateway.goodrich.com (HELO phx-mxgateway.goodrich.com) (63.241.174.69) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 20 Jun 2008 11:44:50 +0000 X-AuditID: ac150e22-ae98dbb000000d06-82-485b98301b70 Received: from GR-GWI-WEST-A.goodrich.com (gr-gwi-west-a.goodrich.com [170.126.245.4]) by phx-mxgateway.goodrich.com (Symantec Mail Security) with ESMTP id D77C3544002; Fri, 20 Jun 2008 07:44:48 -0400 (EDT) Received: from NHC1EX21.goodrich.root.local (localhost [127.0.0.1]) by GR-GWI-WEST-A.goodrich.com (8.13.5/8.13.5) with ESMTP id m5KBiQJ7011765; Fri, 20 Jun 2008 07:44:42 -0400 (EDT) Received: from nhc0ex13.goodrich.root.local ([170.126.245.54]) by NHC1EX21.goodrich.root.local with Microsoft SMTPSVC(6.0.3790.3959); Fri, 20 Jun 2008 07:44:41 -0400 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: sigaction & pthread_sigmask Date: Fri, 20 Jun 2008 11:45:00 -0000 Message-ID: <35737E0536AA3D4BA26F10F103C8ABF809F57F19@nhc0ex13.goodrich.root.local> In-Reply-To: <485B07BB.5060802@homemail.com.au> References: <20080619055744.GA19869@wilbur.25thandClement.com> <35737E0536AA3D4BA26F10F103C8ABF809F131F2@nhc0ex13.goodrich.root.local> <20080619081432.qlk6ka1eogock8kg@webmail.pioneerwireless.ca> <485B07BB.5060802@homemail.com.au> From: "Burkhardt, Glenn" To: "Ross Johnson" , "John E. Bossom" 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/msg00037.txt.bz2 Thank you, Ross. Sorry I wasn't paying closer attention. The timer code is available here: http://ftp.gnu.org/gnu/glibc/glibc-linuxthreads-2.5.tar.bz2 The code I posted is from an older code set, but the current is virtually the same, and is clearly marked with the "GNU Lesser General Public License". In any case, I believe that basic facilities like signals and timers that are bound up in a threads implementation would be a good addition to pthreads-win32. > -----Original Message----- > From: pthreads-win32-owner@sourceware.org=20 > [mailto:pthreads-win32-owner@sourceware.org] On Behalf Of Ross Johnson > Sent: Thursday, June 19, 2008 9:28 PM > To: John E. Bossom > Cc: pthreads-win32@sourceware.org > Subject: Re: sigaction & pthread_sigmask >=20 > The timers code is from the GNU C library, which the comments=20 > in the included header file says is LGPL, so it would be ok to use. >=20 > However, if the contributors to pthreads-win32 were to agree=20 > in future to change to a license other than the LGPL or GPL=20 > then this code would need to be completely removed or replaced. >=20 > Regards. > Ross >=20 > John E. Bossom wrote: > > > > Your contribution has comments that it is licensed under the GNU=20 > > Public License. This, if included in pthreads-win32, would=20 > upsurp the=20 > > LGPL license designation of pthreads-win32 and thus prevent=20 > commercial=20 > > use of pthreads-win32 (something LGPL permits provided it=20 > is used as a=20 > > shared library - use of the static library renders the license GPL,=20 > > though) Are you the original author of this code? Would you=20 > consider=20 > > changing the license? Have you already published the package as GPL? > > > > Ross, comments? > > > > Cheers, > > John. > > > > Quoting "Burkhardt, Glenn" : > > > >> I think so. Semaphores might seem out of scope, but they're an=20 > >> integral part of concurrent programming. Signals need to=20 > be thread=20 > >> smart, so they're naturally part of a thread implementation. > >> So are timers - attached is a pthreads compatible version of Posix=20 > >> timers, but it's lacking the function of sending a signal=20 > to a thread=20 > >> when a timer has expired. > >> > >>> -----Original Message----- > >>> From: pthreads-win32-owner@sourceware.org > >>> [mailto:pthreads-win32-owner@sourceware.org] On Behalf Of William=20 > >>> Ahern > >>> Sent: Thursday, June 19, 2008 1:58 AM > >>> To: pthreads-win32@sourceware.org > >>> Subject: sigaction & pthread_sigmask > >>> > >>> Would it be worthwhile to submit a sigaction, sigwait,=20 > sigprocmask,=20 > >>> pthread_sigmask patch? Or are signals strictly outside=20 > the scope of=20 > >>> the project? > >>> > >>> I'm working on sigaction and sigwait=20 > implementations--using atomic=20 > >>> CAS operations for async-safety--intended for a portable kqueue=20 > >>> library. But the library depends on > >>> pthreads-w32 anyhow, and it would be cleaner to simply=20 > patch upstream. > >>> > >>> > >>> > >> > > > > >=20 >=20