This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


What are the steps required to regenerate libcpp's aclocal.m4?

When testing whether the entire tree could be upgraded to automake 1.9.1, I get errors regarding numerous missing gettext macro's when attempting to regenerate aclocal within libcpp.

Since there is neither an m4 directory nor an acinclude.m4 within libcpp, I've concluded that aclocal.m4 was either handcrafted or there was an included directory on a developer's systems that was not checked into the tree. One thing that leads me to believe that the latter is true is that some of the macros are from gettext 0.13, but we only have a libintl 0.12 our the tree (FWIW, the current gettext's libintl is 0.14.1)

Also now that we are moving to automake 1.9, shouldn't we be split out all the extra macros we use into individual files within a toplevel m4 directory as the automake people recommend? The generated aclocal and configure would become very small if we were to follow that advice.

Kelley Cook


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]