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 Date: Mon, 8 Apr 2002 09:29:24 +0200 From: Corinna Vinschen To: "'cygwin'" Subject: Re: Autoconf 2.53 check for working mmap fails Message-ID: <20020408092924.A24639@cygbert.vinschen.de> Mail-Followup-To: 'cygwin' References: <000001c1dcc0$9cd0b680$0200a8c0 AT sknet01> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000001c1dcc0$9cd0b680$0200a8c0@sknet01> User-Agent: Mutt/1.3.22.1i On Fri, Apr 05, 2002 at 05:40:36PM +0100, (1pH3r_IVI4IV14( wrote: > When configuring a package using autoconf-2.53, the built-in check for > mmap (AC_FUNC_MMAP I believe) fails: > > [...] > checking for working mmap... no > [...] That's expected unfortunately. The mmap test in autoconf (I know this failing test since at least version 2.13) checks the memory mapping using a UNIXism. It tries to mmap() a file to an already area already allocated using malloc(). This is plainly impossible on Win32 where the memory used for mmap must be unallocated and which has to reside in a special memory arae used for mappings. Therefore the autoconf mmap test must fail on Win32. 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/