From: Cesar S. <ces...@gm...> - 2007-05-08 10:56:23
|
Vincent Torri wrote: > Hello, > > I have installed autoconf 2.60 on windows with MSYS/MinGW in /usr. But it > returns that error when I use it: > > /bin/autoconf: /home/vincent/libdvi/D:/msys/1.0/bin/autom4te: No such file or > directory > /bin/autoconf: exec: /home/vincent/libdvi/D:/msys/1.0/bin/autom4te: cannot > execute: No such file or directory > > that is, autoconf prepends the current location where i'm using it to the > directory of autom4te. > > I also can't install automake because of the same problem. > > same problem with the 2.61 version. > How did you invoke the configure script? I saw this problem in the past, when I used DOS paths in the configure line (--prefix=`cd /mingw && pwd -W`). A solution was to use the POSIX path (--prefix=/mingw). I believe this is because autoconf is interpreted by perl, which is a MSYS application, and has POSIX semantics. Try this: make distclean ./configure --prefix=/usr make install Does it helps? > > Another question about the path : the configure script deplace /usr by the real > windows path. Why ? The problem is that, when running automake, I get an error, > because of the following command in automake: > > BEGIN > { > my $perllibdir = $ENV{'perllibdir'} || 'D:/msys/1.0/share/automake-1.10'; > unshift @INC, (split ':', $perllibdir); > > so it removes the ':' > This should be solved by the above, also. Regards, Cesar |