Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 20 Dec 2004 13:12:50 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [Fwd: [sem_* functions in cygwin]] Message-ID: <20041220121250.GA10286@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20041209164442 DOT GA25246 AT cygbert DOT vinschen DOT de> <41BC4DA5 DOT 9000800 AT familiehaase DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41BC4DA5.9000800@familiehaase.de> User-Agent: Mutt/1.4.2i [Oops, I've sent this to Gerrit by PM instead of to the list. Just resending it now for the records] On Dec 12 14:54, Gerrit P. Haase wrote: > Corinna Vinschen wrote: > >>----- Forwarded message from "Gerrit P. Haase" ----- > >>nearly all sem_* functions are available, but sem_unlock is missing, > >>was there a problem implementing sem_unlock() or was it just missed > >>by accident? > >>Gerrit > >>----- End forwarded message ----- > > > >I guess you're asking about sem_unlink(). It's not implemented so far > >since named POSIX semaphores are implemented using named Windows > >semaphores. The SUSv3 description contains a pretty unfortunate > >implementation detail: > > > > Calls to sem_open() to recreate or reconnect to the semaphore refer > > to a new semaphore after sem_unlink() is called. > > > >There's no way I know of, which allows to implement this using named > >Windows semaphores. At least not without adding a lot of annoying > >bookkeeping overhead, possibly involving cygserver. > > I got an undefined reference to sem_unlock(). There's no such function defined in SUSv3. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/