Re: New vs. installed .m4 macro

[Tom Tromey]

>>>>> "Alexander" == Alexander Mai <address@hidden> writes:

Alexander> We have some auto* macros which we want to have in their
Alexander> own .m4 files, e.g. ac_find_xpm.m4.

Alexander> They "somehow" made their way into my ~/share/aclocal/
Alexander> directory. Now when I try to re-create e.g. lib/Xlt/aclocal.m4
Alexander> aclocal either takes only the pre-installed macro or at best
Alexander> I can force (by using "-I .") to have a warning about a 
Alexander> duplicate macro definition. It however again takes the old, 
Alexander> installed version :-(

Alexander> Either aclocal/automake would be a bit short-minded in its design
Alexander> or I haven't understood the docs fully and miss the proper
Alexander> way to handle this situation. The --acdir is a bit too strong,
Alexander> and doesn't seem to be useful here.

Yes, aclocal is short-sighted.  You should either remove one copy of
the .m4 files, or use a single m4 directory, or something like that.
In the long term we plan to get rid of aclocal.  It has proved to be a
source of trouble.

Tom