The African Chief wrote:
Like I said before, I can't do anything with "configure" under Win32. The system simply fails to recognise the script as something that it can execute.
Maybe the script expects a program "\bin\sh.exe" because the first line reads "#!/bin/sh". This problem once occured under DJGPP ...
This is so even when trying to run the script under Bash. Since this script seems really to be a unix thing, perhaps an alternative could be made for non-unix systems? - basically, either to translate the "configure" script into batch commands that the Dos or Windows command interpreters can process (which is probably impossible, because the script seems too complex to translate into a Dos batch file) or to write a Pascal (or C) program that does everything that the "configure" script does. [...]
The second thing would be possible but unwise: The script is generated automatically and re-built with each version of GCC.
The right solution would be to make `mingw32' complete enough to run the script (as has been done for DJGPP). Besides `bash', the "text utils" and "shell utils" are needed (see DJGPP).
What I did in fact do for EMX where I also could not run the `configure' script was to generate `Makefile', `p/Makefile', `p/rts/Makefile' and (IIRC) some `*config*.h' files manually (by manually changing the corresponding `*.in' files while looking what `configure' had done before for Linux). The same can certainly be done for mingw32 - of course with the drawback that the work has to be repeated each time the underlying GCC version changes.
(Nevertheless it can be an interesting exercise to do this work now for gcc-2.8.1 or egcs-1.1.2 and repeat it in a few days/weeks when GPC can run with gcc-2.95.x.;-)
PS: Perhaps I can get bash to run the script. If I try to run "configure.in", bash seems to start trying to run it, and then finally chokes. However, with "configure", it just says that the file does not exist - which is not true. 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' means "eXecutable".
If so, what parameters do I pass to "chmod" so as to change the attributes of "configure" to the same one as "configure.in"?
chmod +x configure.in
But it will not run.
Greetings,
Peter