[prev in list] [next in list] [prev in thread] [next in thread]
List: cygwin-apps
Subject: Re: don't use AC_FUNC_MMAP, use AC_CHECK_FUNCS(mmap) instead.
From: Yaakov Selkowitz <yselkowitz () users ! sourceforge ! net>
Date: 2004-10-17 2:19:33
Message-ID: 4171D6B5.60107 () users ! sourceforge ! net
[Download RAW message or body]
-----BEGIN PGP SIGNED MESSAGE-----
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 configure.ac:
| case "$host" in
| *cygwin*)
| AC_CHECK_FUNCS(mmap)
| ;;
| *)
| AC_FUNC_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 - http://enigmail.mozdev.org
iD8DBQFBcda0piWmPGlmQSMRApK5AJ9xJ0PIjRNAD02kiJthDlcuTaA7rQCeOyGf
weDS0UB1nDh1Z/374yVYrQg=
=uCgn
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic