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 Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 15 Mar 2002 09:35:31 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: struct flock, off_t, and __CYGWIN_USE_BIG_TYPES__ Message-ID: <20020315093531.G31148@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i On Thu, Mar 14, 2002 at 05:29:52PM -0800, Matt Seitz wrote: > I am porting a program that assumes 32-bit gid/uid, so I defined > __CYGWIN_USE_BIG_TYPES__. Unfortunately, that is causing my compiler to > compain when I try to assign an off_t value to the l_start or l_len fields > of struct flock. It appears this is because l_start and l_len are hard > coded as 32-bit longs, while off_t can be 32-bit or 64-bit depending on > whether __CYGWIN_USE_BIG_TYPES__ is defined. I assume I can't simple > redefine struct flock without having to rebuild cygwin.dll. What is the > best solution to this problem? It won't work. Forget about it. Don't set __CYGWIN_USE_BIG_TYPES__. Don't touch it. Let it alone. Don't call us, we call you. There is actually a reason that we didn't publish this define! This is work in progress, it isn't finished and it can't work in the current state of development. Recompiling Cygwin will not help at all. Besides that, the application programmer will *never* have to set this define by him/herself. At one point in future we'll switch over to 64 bit off_t and 32 bit uid_t and gid_t and then *we* will set that define once and for all. In the meantime you're stuck with 16 bit uid_t and gid_t types, unfortunately. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/