10-Sep-99 10:57 you wrote:
Peter Gerwinski once wrote:
The normal procedure is to type first `./configure' and then `make LANGUAGES=pascal' in the GCC directory that contains the GPC source in a subdirectory `p'. However I know that mingw32 needs special care.
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. 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. I would do this myself (i.e., translate into a Pascal program) if I understood the script - but I don't (at least, not most of it).
configure is created from configure.in in not-trivial preprocessing and I think that it's far better to try and find out why you can not execure it with bash then try to convert in in something compatible with Win32. It SHOULD work in cygwin environment.
Does this seem a feasible option, or am I barking up the wrong tree here? If it is feasible, does anyone wish to take up the task?
This is way to complex task to even think about it. Better try to find out why you can not execute script.
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.
Since you should not execute configure.in ...
However, with "configure", it just says that the file does not exist - which is not true.
I bet it's 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" is "executable" bit. So in normal (unix-like OS) you can execute configure but not configure.in ... Execute with just "./configure" command taht is.
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 a-x
And then configure will not be executable (just like configure.in is now).
Are you shure you have bash accessible as /bin/sh ? Since configure starts with "#!/bin/sh" cygwin will try to execute it with /bin/sh and if it's not there you'll see "file does not exist" message. I bet it's exactly what happens...