This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: don't use AC_FUNC_MMAP, use AC_CHECK_FUNCS(mmap) instead.

Hash: SHA1

Gerrit P. Haase wrote:
|> AC_CHECK_FUNCS(mmap) issues this:
|> checking for mmap... yes
|> This is what I will using now for all the GNOME packages, there are
|> several packages affected, so far I know of:
|> - libgtop
|> - gtk+
|> - libgnomeprint
|> - libgsf

Actually, looking again at my libgnomeprint22 package, I already had
manually patched the few places that needed mmap (i.e.
#if defined(HAVE_MMAP) || defined(__CYGWIN__)
) due to build errors.  I'll have to look at libgsf though.

|> I think it just tries to link against the system library and it
|> succeeds, so mmap() is considered to be available.  Fine with me.
|> Using the macro AC_FUNC_MMAP, the test fails and mmap() will not be
|> available.
| BTW, it looks like this in
| case "$host" in
|   *cygwin*)
|     AC_CHECK_FUNCS(mmap)
|     ;;
|   *)
|     ;;
| esac

Thanks for the tip.  But how does that define HAVE_MMAP?  And what about
fixing AC_FUNC_MMAP itself?

Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Cygwin) Comment: Using GnuPG with Thunderbird -


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]