On May 29, 2001, "Tim Van Holder" <[EMAIL PROTECTED]> wrote:
> If AM_MISSING_PROG actually checks
> for the program in question before using 'missing --run $program', there
> would be no such problem.
The point is to avoid having to test for the program at configure
time, since only developers are going to need it and, for them, the
overhead of a PATH search done by the shell at `missing' execution
time is probably no big deal, whereas looking for a number of
auxiliary tools that are not going to be used for random installations
takes a significant amount of time on slow platforms.
--
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
