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 Subject: RE: MIT shared memory extension MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 17 May 2002 23:34:45 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Ralf Habacker" , "cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4HENAV31413 > -----Original Message----- > From: Ralf Habacker [mailto:Ralf DOT Habacker AT freenet DOT de] > Sent: Friday, May 17, 2002 9:58 PM > To: Robert Collins; cygwin > Subject: RE: MIT shared memory extension > > > > > Thats all. No patching headers. This enables migrating > one package > > > to cygwin ipc stuff, while other packages could use the cygipc > > > stuff. > > > > We still need to do the ABI upgrade though, before that can be done. > > You mean building a new cygwin1.dll with shm support ? No, I meant a new cygwin1.dll with 64bit key_t. However your types.h patch will also do the job of allowing smooth transition. > What's additional to do ? Finish the cygwin code :}. > So the only thing to do I see is to distribute a new cygwin > release with shm support. I don't think that the next cygwin release should enable the code. It's not ready yet - it's apparently high latency, and needs further work. > BTW: What about a new binutils release. Is this going on ? I'm not sure I haven't personally had time to review the pending patches yet. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/