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 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Subject: sem_getvalue patch Date: Fri, 7 Jun 2002 00:56:47 -0400 Message-ID: <3D848382FB72E249812901444C6BDB1D0BA91A@exchange.timesys.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robb, Sam" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id g574wrv09125 Folks, I was seeing how well the latest version of arts compiled under Cygwin, and noticed that the only real complaint was the lack of sem_getvalue()... so I took the dive, fetched the latest Cygwin source from CVS, and poked around to see what needed to be done. With a little effort, I've managed to build a cygwin1.dll that exports sem_getvalue(). The version of cygwin1.dll that I built seems subtly hosed, though - while I can compile and run my test program from within a Windows cmd.exe shell, trying to run bash or ls (and probably a great many other things) hangs. So, a couple of questions: 1) What's wrong with my cygwin1.dll? Did I miss some special magic I need to do in addition to adding an export to cygwin.din? 2) Assuming that I can resolve the apparent export problem and produce a working cygwin1.dll, is there any interest in a patch for sem_getvalue()? Or was it left unimplemented for a reason (other than lack of need/time?) Thanks, -Samrobb