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 Date: Mon, 10 Mar 2003 16:46:26 +0100 From: Corinna Vinschen To: cygwin-developers AT cygwin DOT com Subject: Re: HEADSUP everyone: 32/64bit changes are commited Message-ID: <20030310154626.GZ1193@cygbert.vinschen.de> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20030309222706 DOT GS1193 AT cygbert DOT vinschen DOT de> <20030309235923 DOT GA14106 AT redhat DOT com> <20030310111321 DOT GV1193 AT cygbert DOT vinschen DOT de> <3E6C9C1E DOT B326D8C8 AT ieee DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E6C9C1E.B326D8C8@ieee.org> User-Agent: Mutt/1.4i On Mon, Mar 10, 2003 at 09:07:26AM -0500, Pierre A. Humblet wrote: > Corinna Vinschen wrote: > > I've just posted the patch to newlib (Subject: "[PATCH] Avoid more > > problems with type clashes"). Everybody who wants to build Cygwin > > from CVS should apply this patch as long as it's not approved and > > commited. > > FYI, I tried to rebuild everything last night on Windows but the dll build > failed because fopen64 and friends were missing from libc (although stdio64 > is there and I ran configure on newlib). I've now rebuild from scratch multiple times and IWFM. Details? > Also I realized recently we are heading for trouble with lastlog. > It's really an array of ~200 byte structures indexed by uid. Currently > its max size is ~ 200 x 64k = 13MB. With the change it can be 800 GB or so. I'm using uid 100003 currently and mine is 271K in size. Under the assumption that uids are growing monotonically on NT systems, I guess we'll have some time to think about a change. The bigger problem will be to update all Cygwin packages quick enough so that the upgrade is more or less smooth. As long as ssh and inetutils aren't rebuild, this problem won't happen at all. Worse: People with uids > 64K will be unable to login for no apparent reason (from the users perspective). Btw., I just found that the wtmp/utmp handling in syscall.cc is still using 32bit offsets. I guess we will find a few more of this quirks in Cygwin until we can eventually release the next version... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc.