ok... I feel silly now, but have been unable to successfully execute a fairly simple Bourne Shell script and am frustrated.

Anyway, the script reports "Bourne shell script text" when I call 'file' one it.

It does begin w/ #! bin/sh

Yet, when I go to the directory w/ the shell script, hit
./configure ("configure" being the name of the file), I get
./configure: Command not found.

I'm certain it is a valid Bourne shell script, and it definitely works on other Unices. Is there something I am doing wrong? Could it be a result of it not working with OS X for some reason? The error seems to indicate that it simply doesn't even try to execute the script because it doesn't think it's valid as a script file.

Oh.... I also ran chmod 777 configure, and verified that I have execute permission.

Please help! I guess I am probably missing something simple, but I can't think of it for my life right now. I really want to get this working. I tried running it through bash, too, in the same way and bash reported the same error.


Thanks,
Eric
eaw01998@pomona.edu

Originally posted by ericw:
ok... I feel silly now, but have been unable to successfully execute a fairly simple Bourne Shell script and am frustrated.

Anyway, the script reports "Bourne shell script text" when I call 'file' one it.

It does begin w/ #! bin/sh

Yet, when I go to the directory w/ the shell script, hit
./configure ("configure" being the name of the file), I get
./configure: Command not found.

I'm certain it is a valid Bourne shell script, and it definitely works on other Unices. Is there something I am doing wrong? Could it be a result of it not working with OS X for some reason? The error seems to indicate that it simply doesn't even try to execute the script because it doesn't think it's valid as a script file.

Oh.... I also ran chmod 777 configure, and verified that I have execute permission.

Please help! I guess I am probably missing something simple, but I can't think of it for my life right now. I really want to get this working. I tried running it through bash, too, in the same way and bash reported the same error.


Thanks,
Eric
eaw01998@pomona.edu

Eric

The 'command not found' be relate to a command in the script, as opposed to the script itself.

It may be the first line, which presuming your message isn't a typo should read :

#!/bin/sh

You had it without the initial '/' which makes it a relative path to the directory that configure is in.

If that was a typo then check the paths for the executables in the script

The pope

oops... that was a typo...

#!/bin/sh

is the first line. What paths should I look for?

Eric

heh... just kidding. turns out one of the foolders it needed wasn't in the right place


Thanks for the suggestion!

eric