This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libcpp's aclocal.m4 regeneration question. Also is it time for a toplevel "m4" directory?
- From: Zack Weinberg <zack at codesourcery dot com>
- To: kcook at gcc dot gnu dot org
- Cc: GCC Mailing List <gcc at gcc dot gnu dot org>, Paolo Bonzini <bonzini at gnu dot org>
- Date: Mon, 23 Aug 2004 18:01:02 -0700
- Subject: Re: libcpp's aclocal.m4 regeneration question. Also is it time for a toplevel "m4" directory?
- References: <20040823205214.97921.qmail@web41510.mail.yahoo.com>
Kelley Cook <kcook@gcc.gnu.org> writes:
>> produces an aclocal.m4 which is identical to the one currently
>> checked in.
>> The reason there is no m4/ nor acinclude.m4 is, everything comes from
>> ../config or from /usr/share/aclocal.
>
> Yes, but this is because your /usr/share/aclocal likely contains a few
> macros from your system's already installed gettext (which is later
> than 0.12).
Well, yes, but I'm not sure what your point is.
> IMO, we should import all of GCC's required gettext macros into the
> toplevel config (or m4) directory.
Sure, good idea.
zw