> On Wed, Sep 24, 2003 at 02:19:06PM +0200, Akim Demaille wrote: >> At the origin I was considering that AC_CONFIG_M4_DIR was >> automatically passed to m4 as a -I, so instead of >> m4_include([config/init.m4]) etc. you'd have m4_include([init.m4]).
> Isn't there a chicken'n'egg problem? How can you trace for > AC_CONFIG_M4_DIR if you need the result to run m4 properly?
Right, there was something like that :)
With m4-2.0 (it is too different to 1.4 to be called 1.5), you (or I) could write a builtin for include path mangling. Provided AC_CONFIG_M4_DIR([config]) expanded to (say) m4_prepend_search_path([config]),
and that happened before the first m4_include, it would work.
I'd quite like to sort out m4's search path issues in the near future... patches gratefully accepted :-)
Cheers, Gary. -- ())_. Gary V. Vaughan gary@(lilith.warpmail.net|gnu.org) ( '/ Research Scientist http://www.oranda.demon.co.uk ,_())____ / )= GNU Hacker http://www.gnu.org/software/libtool \' `& `(_~)_ Tech' Author http://sources.redhat.com/autobook =`---d__/
