Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <006501c2e5d7$e7135b50$0400a8c0@robertcollins.net> Reply-To: "Cygwin \(Robert Collins\)" From: "Cygwin \(Robert Collins\)" To: References: <20030308164426 DOT GK1193 AT cygbert DOT vinschen DOT de> Subject: Re: HEADS UP cygserver maintainers Date: Sun, 9 Mar 2003 12:04:57 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 === ----- Original Message ----- From: "Corinna Vinschen" To: Sent: Sunday, March 09, 2003 3:44 AM Subject: HEADS UP cygserver maintainers > Hi, > > cygserver_shm.cc is still using uid_t and gid_t datatypes. This must > be changed to either __uid16_t/__gid16_t or __uid32_t/__gid32_t. Since > the datatypes uid_t and gid_t are changing their size according to the > definition of __CYGWIN_USE_BIG_TYPES__ (see include/cygwin/types.h), > their usage is disallowed inside of Cygwin (as is e. g. off_t as well). > > It would be helpful to correct this as soon as possible. I guess since > cygserver isn't really used so far, it doesn't make sense to use the > old 16 bit datatypes anymore but instead to define these functions > just with 32 bit types. Yep, I agree - 32 bit should be used in cygserver. (How do we handle compatability with 16 bit client programs though? Or do we require that they are compiled with 32-bit?) I don't mean existing binaries - they can simply recompile. As for who does this, I'll try to make time :[. (Adds to the queue..) Rob