wangbookbin | 24 Nov 08:03 2007
Picon

[Autoconf.in]Error 1:The system cannot find the path

$ m4 --version
m4 <GNU M4> 1.4.10
Copyright <C>  2007 Free Software Foundation,Inc.
....................................
$which m4
/usr/local/bin/m4
$ cd autoconf-2.61
$ ./configure --prefix=/usr
................................
$ make
Making all in bin
.................................
The system cannot find the path specified.
autom4te: need GNU m4 1.4 or later: /usr/local/bin/m4
make[1]: ***[autoconf.in] Error 1
make[1]: Leaving directory '/ecos-c/DJGPP/Autoconf/autoconf-2.61/bin'
make: *** [all-recursive] Error 1
 
wangbookbin
e-mail:wang.bookbin <at> msa.hinet.net
2007/11/24  03:03 PM
 
_______________________________________________
Bug-m4 mailing list
Bug-m4 <at> gnu.org
http://lists.gnu.org/mailman/listinfo/bug-m4
Eric Blake | 30 Nov 14:07 2007
Picon

Re: [Autoconf.in]Error 1:The system cannot find the path


According to wangbookbin on 11/24/2007 12:03 AM:
> $ m4 --version
> m4 <GNU M4> 1.4.10
> Copyright <C>  2007 Free Software Foundation,Inc.
> ....................................
> $which m4
> /usr/local/bin/m4
> $ cd autoconf-2.61
> $ ./configure --prefix=/usr
> ................................
> $ make
> Making all in bin
> .................................
> The system cannot find the path specified.
> autom4te: need GNU m4 1.4 or later: /usr/local/bin/m4
> make[1]: ***[autoconf.in] Error 1
> make[1]: Leaving directory '/ecos-c/DJGPP/Autoconf/autoconf-2.61/bin'
> make: *** [all-recursive] Error 1

Thanks for the report.  However, this is not an m4 bug, but an autoconf
one.  And in the meantime, the latest git version of autoconf has changed
its algorithm for detecting m4 at configure time so that it will try
harder (in 2.61, it gave up if the first m4 found was inadequate).  The
main reason that autoconf 2.62 has not been released yet is that we are
awaiting clarification of the licensing exception to guarantee that
autoconf (now GPLv3+) can be used with GPLv2 projects.

However, since it appears that /usr/local/bin/m4 was the first m4 found,
and that it is m4 1.4.10, and also that autom4te doesn't like it, we would
need to see the config.log to figure out why autom4te wasn't happy with m4.

It also appears that you are on Windows, and it appears that you have a
hodge-podge of GNU and other free tools.  Perhaps the interaction between
ecos and DJGPP, along with whatever perl you are using, is making it so
that you don't have a consistent environment for handling POSIX-style
paths.  I would recommend considering the cygwin project, where autoconf,
m4, perl, and other programs are all available in a single project, and
thus work together out of the box rather than requiring you to configure
each tool separately.

--
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9 <at> byu.net

Gmane