libcpp's aclocal.m4 regeneration question. Also is it time for a toplevel "m4" directory?

Zack Weinberg zack@codesourcery.com
Tue Aug 24 02:55:00 GMT 2004


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



More information about the Gcc mailing list