On Aug 4, 2000, Bernard Dautrevaux <[EMAIL PROTECTED]> wrote:
> In this case the problem is not AMA or m4/*.m4; it's usually fixing some
> macros that wrongly run some tests. Waht in this case IS needed is an
> acllocal-like tool that understand the way the package was built (AMA/split
> files) but is able to update simply a give set of AC_XXX macros (let call
> this a module).
> Oh I hear you: I can patch aclocal.m4 !-)
The aim is that Rand Porter gets the original m4 file, patches it, and
does something like:
[aclocal|autoreconf] --update -I /path/to/directory/with/patched/files
on any packages affected.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
