On Jan 31, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote: > ``How stupid configure is not > to check that this executable is not a directory!''. > I'd suggest to fix the second issue :) Sure, it should be fixed. But you'll probably remember I have always opposed the idea of having a directory named m4. -- 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
- Re: autoconf 2.49c fails if '.' is in PATH Alexandre Oliva
- Re: autoconf 2.49c fails if '.' is in PATH Gary V. Vaughan
- Re: autoconf 2.49c fails if '.' is in PATH Akim Demaille
- Re: autoconf 2.49c fails if '.' is in PATH Alexandre Oliva
- Re: autoconf 2.49c fails if '.' is in PATH Akim Demaille
- Re: autoconf 2.49c fails if '.' is in PATH Alexandre Oliva
- Re: autoconf 2.49c fails if '.' is in PATH Akim Demaille
- RE: autoconf 2.49c fails if '.' is in PATH Tim Van Holder
- Re: autoconf 2.49c fails if '.' is in PATH Alexandre Oliva
- RE: autoconf 2.49c fails if '.' is in PATH Bernard Dautrevaux
- Re: autoconf 2.49c fails if '.' is in PATH Akim Demaille
- Re: autoconf 2.49c fails if '.' is in PATH Richard Dawe
- Re: autoconf 2.49c fails if '.' is in PATH Akim Demaille
- Re: autoconf 2.49c fails if '.' is in PATH Earnie Boyd