> > Do not use aclocal.m4 in these subdirectories. Simply add
> > m4_include([../aclocal.m4]) and maybe m4_include([../ltdl.m4])
> > at the top of all these configure.ac.
>
> Not an option since all of the automake macros need to be copied in for
> configure.ac to be expandable to a working con
Alexandre Duret-Lutz wrote:
On Mon, Sep 22, 2003 at 06:12:50PM +0100, Gary V. Vaughan wrote:
[...]
I was hoping to remove acinclude.m4 and use m4_include in aclocal.m4 by
switching to CVS automake, but currently the contents are still copied to
aclocal.m4 if they are not in the same directory as co
>> The autoconf part of this feature is trivial (I can provide a patch if
>> that's useful), but I suspect I'd need to be able to write perl to
>> implement the aclocal end :-)
> Fortunately, if we consider relative directories as local, we don't
> need to look at AC_CONFIG_M4_DIR. Adding t
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 tra
> 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? Ho
Akim Demaille wrote:
> 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
