Doing "ls -all config*" shows that the attributes of "configure.in" are "-rw-r--r--", while those of "configure" are "-rwxr-xr-x". Is the difference significant?
Yes. "x" is "executable" bit. So in normal (unix-like OS) you can execute configure but not configure.in ... Execute with just "./configure" command taht is.
To be sure, in DJGPP you have two ways to "run configure"
- first way: first boot bash from dos prompt (e.g. >), by typing e.g.
bash -login
when you have the bash prompt (e.g. $) you type $ ./configure --prefix=c:/djgpp
-second way directly from dos prompt type simply:
bash configure --prefix=c:/djgpp
Both methods work. --prefix is mandatory because the default is /usr/local which does not exist under DOS. What are you doing exactly?
On the other hand you need to create sh.exe from bash.exe In djgpp you have two ways
copy bash.exe sh.exe
or make a symlink
ln -s bash.exe sh.exe
the second is more economical because it creates only a short file (2048 bytes) which calls bash, but both work. In djgpp bash translates silently
/bin/sh
to
%DJDIR%/bin/sh
i.e. for example
c:/djgpp/bin/sh
I don't know what it does under mingw32, but this is certainly crucial.
Any how you could try to circumvent it by putting sh.exe in a dir /bin directly at root of your disk.