This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: How is aclocal.m4 in gcc maintained?
- From: "H. J. Lu" <hjl at lucon dot org>
- To: Nathanael Nerode <neroden at doctormoo dot dyndns dot org>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 2 Jul 2002 21:37:47 -0700
- Subject: Re: How is aclocal.m4 in gcc maintained?
- References: <20020703042622.GA19875@doctormoo.dyndns.org>
On Wed, Jul 03, 2002 at 12:26:22AM -0400, Nathanael Nerode wrote:
> HJ, there's a file 'config/acinclude.m4' in the top level. Rather than
> introducing a new accross.m4 file, why not put the macros in
> config/acinclude.m4? That's already supposed to be included by other
> acinclude.m4 or aclocal.m4 files.
That will generate very different aclocal.m4 for fastjar and libffi.
But I don't mind moving accross.m4 into config.
>
> Directories which *don't* have their own acinclude.m4 are
> mostly directories which *don't* use Automake. Fastjar seems to be a
> bizarre exception, and probably should have an acinclude.m4.
>
> gcc in particular does *not* use Automake. I believe it *already*
> includes config/acinclude.m4 (though I'm not sure). So if you added the
I didn't see.
> new AC_COMPILE_CHECK_SIZEOF to config/acinclude.m4 you could immediately
> start using in in gcc/aclocal.mr.
>
H.J.