From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12010 invoked by alias); 20 Jun 2008 11:48:18 -0000 Received: (qmail 12001 invoked by uid 22791); 20 Jun 2008 11:48:17 -0000 X-Spam-Check-By: sourceware.org Received: from pioneerwireless.ca (HELO pioneerwireless.ca) (72.172.130.178) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 20 Jun 2008 11:47:44 +0000 Received: (qmail 31160 invoked by uid 48); 20 Jun 2008 07:47:42 -0400 Received: from 24.139.16.66 ([24.139.16.66]) by webmail.pioneerwireless.ca (Horde MIME library) with HTTP; Fri, 20 Jun 2008 07:47:42 -0400 Message-ID: <20080620074742.trbpj9w68gsg044o@webmail.pioneerwireless.ca> Date: Fri, 20 Jun 2008 11:48:00 -0000 From: drifting@pioneerwireless.ca To: pthreads-win32@sourceware.org Subject: RE: sigaction & pthread_sigmask References: <20080619055744.GA19869@wilbur.25thandClement.com> <35737E0536AA3D4BA26F10F103C8ABF809F131F2@nhc0ex13.goodrich.root.local> <20080619081432.qlk6ka1eogock8kg@webmail.pioneerwireless.ca> <485B07BB.5060802@homemail.com.au> <35737E0536AA3D4BA26F10F103C8ABF809F57F19@nhc0ex13.goodrich.root.local> In-Reply-To: <35737E0536AA3D4BA26F10F103C8ABF809F57F19@nhc0ex13.goodrich.root.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.5) 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/msg00038.txt.bz2 Sorry for the confusion... I forgot that the LGPL had a different name in the past.... Quoting "Burkhardt, Glenn" : > 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 >> [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 >> >> The timers code is from the GNU C library, which the comments >> in the included header file says is LGPL, so it would be ok to use. >> >> However, if the contributors to pthreads-win32 were to agree >> in future to change to a license other than the LGPL or GPL >> then this code would need to be completely removed or replaced. >> >> Regards. >> Ross >> >> John E. Bossom wrote: >> > >> > Your contribution has comments that it is licensed under the GNU >> > Public License. This, if included in pthreads-win32, would >> upsurp the >> > LGPL license designation of pthreads-win32 and thus prevent >> commercial >> > use of pthreads-win32 (something LGPL permits provided it >> is used as a >> > shared library - use of the static library renders the license GPL, >> > though) Are you the original author of this code? Would you >> consider >> > 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 >> >> integral part of concurrent programming. Signals need to >> be thread >> >> smart, so they're naturally part of a thread implementation. >> >> So are timers - attached is a pthreads compatible version of Posix >> >> timers, but it's lacking the function of sending a signal >> to a thread >> >> when a timer has expired. >> >> >> >>> -----Original Message----- >> >>> From: pthreads-win32-owner@sourceware.org >> >>> [mailto:pthreads-win32-owner@sourceware.org] On Behalf Of William >> >>> 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, >> sigprocmask, >> >>> pthread_sigmask patch? Or are signals strictly outside >> the scope of >> >>> the project? >> >>> >> >>> I'm working on sigaction and sigwait >> implementations--using atomic >> >>> CAS operations for async-safety--intended for a portable kqueue >> >>> library. But the library depends on >> >>> pthreads-w32 anyhow, and it would be cleaner to simply >> patch upstream. >> >>> >> >>> >> >>> >> >> >> > >> > >> >> >