martin wrote:
>
> The exact message is : bash: ./configure: bad interpreter: No such file
> or directory
Just a gues but this seems to mean that the correct shell interpreter
for the script cannot be found. Which is strange since you are using
bash ...
Is the first line of your configure file:
#! /bin/sh
If not that would be a problem ...
If it is what do you get if you do:
$ which sh
You should get something like:
$ which sh
/bin/sh
If you get something like:
/usr/bin/which: no sh in .....
Then there is something strange about your system ;)
Jean-Christian Imbeault