All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 1/4] autoconf: Check for working mmap
Date: Fri, 04 Aug 2006 21:02:07 +0200	[thread overview]
Message-ID: <eb05i7$3d6$1@sea.gmane.org> (raw)
In-Reply-To: 7vodv0jpo1.fsf@assigned-by-dhcp.cox.net

Junio C Hamano wrote:

> Jakub Narebski <jnareb@gmail.com> writes:
> 
>> Use AC_FUNC_MMAP check to check if the `mmap' function exists and
>> works correctly.  (It only checks private fixed mapping of
>> already-mapped memory.)
> 
> This tests something we do not really care about (we do not
> mmap MAP_FIXED, and not over an already allocated space).

Well, I have noticed that there exist AC_FUNC_MMAP, used it, 
then read about its limitations.

Is there any platform that passes this test, but needs NO_MMAP?
If so, then disregard this patch.
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2006-08-04 19:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04 10:12 What's in git.git Junio C Hamano
2006-08-04 10:27 ` Jakub Narebski
2006-08-04 15:55 ` [PATCH 1/4] autoconf: Check for working mmap Jakub Narebski
2006-08-04 18:56   ` Junio C Hamano
2006-08-04 19:02     ` Jakub Narebski [this message]
2006-08-04 15:55 ` [PATCH 2/4] autoconf: Check for ll hh j z t size specifiers introduced by C99 Jakub Narebski
2006-08-04 15:55 ` [PATCH 3/4] autoconf: Typo cleanup, reordering etc Jakub Narebski
2006-08-04 15:55 ` [PATCH 4/4] Copy description of new build configuration variables to configure.ac Jakub Narebski
2006-08-04 18:40 ` What's in git.git Johannes Schindelin
2006-08-04 18:55 ` Jakub Narebski
2006-08-04 19:09   ` Junio C Hamano
2006-08-04 19:50     ` Junio C Hamano
2006-08-04 20:06       ` Junio C Hamano
2006-08-04 20:27       ` Jakub Narebski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='eb05i7$3d6$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.