Entry

When I run ./configure -..., i get "bash: configure: bad interpreter". Why?

Oct 30th, 2004 10:43
Francisco de Jesus Orozco, John Lim, Michael Potter,

1. Check the first line of the ./configure file. It should be something 
like
#! /bin/sh
Check that the /bin/sh file exists and that it works :-)
2. You could have unpacked it using WinZip or some similar tool that 
adds invisible carriage returns. In WinZip, turn off TAR smart CR/LF 
conversion and unpack the file again.
3. Check the mount option for the filesystem where you are running the
script from, with the command 
mount
for example, it could give: 
/dev/sda2 on / type ext3 (rw)
/dev/sda5 on /tmp type ext3 (rw)
/dev/sda6 on /var type ext3 (rw)
/dev/sda7 on /home type ext3 (rw,noexec,nosuid,nodev)
As you can see, /home has the noexec attribute, so you can't run scripts
or programs stored there.
To run scripts, you could use directly the shell
   bash configure
but as this script creates programs and store them in the same tree, the
process will fail,  so is better to move the source tree to another
filesystem, for example under /usr/src/install, and  build there.