This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch]: use mmap.m4 in gcc/configure
- From: Paolo Bonzini <pbonzini at redhat dot com>
- To: Tristan Gingold <gingold at adacore dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 03 Apr 2012 12:09:26 +0200
- Subject: Re: [Patch]: use mmap.m4 in gcc/configure
- References: <597915CC-4C96-4276-B78D-520D894A4916@adacore.com>
Il 03/04/2012 11:25, Tristan Gingold ha scritto:
> Hi,
>
> the gcc_AC_FUNC_MMAP_BLACKLIST function in gcc/acinclude.m4 is exactly the same as the GCC_AC_FUNC_MMAP_BLACKLIST function in config/mmap.m4 (except the case of the first three letters). This patch makes gcc/configure.ac uses config/mmap.m4 instead of its own version.
>
> Also, I modified config/mmap.m4 to match *vms* instead of vms* like all other configuration scripts (because the official name is now openvms).
>
> Tested by building for ia64-hp-openvms and by visual inspection of the generated configure (only the *vms* lines changed).
>
> Ok for trunk ?
>
> Tristan.
>
> config/
> 2012-04-03 Tristan Gingold <gingold@adacore.com>
>
> * mmap.m4: Use *vms* instead of vms*.
>
> gcc/
> 2012-04-03 Tristan Gingold <gingold@adacore.com>
>
> * configure.ac: Use GCC_AC_FUNC_MMAP_BLACKLIST instead
> of gcc_AC_FUNC_MMAP_BLACKLIST.
> * aclocal.m4: Include mmap.m4
aclocal.m4 is supposed to be automatically generated, can you check that
nothing strange happens if you configure with --enable-maintainer-mode
and do "touch acinclude.m4 && make aclocal.m4" in the GCC directory?
> * acinclude.m4 (gcc_AC_FUNC_MMAP_BLACKLIST): Remove.
> * Makefile.in (aclocal_deps): Add mmap.m4.
> * configure: Regenerate.
>
> libitm/
> 2012-04-03 Tristan Gingold <gingold@adacore.com>
>
> * configure: Regenerate.
Ok.
Paolo