LinuxQuestions.org - ./configure - not found, but file exist

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - ./configure - not found, but file exist (https://www.linuxquestions.org/questions/linux-general-1/configure-not-found-but-file-exist-130618/)

./configure - not found, but file exist

Here is the problem:

Code:

(23:06:53)[ivanatora@~/Archives/cube/source/cube_2003_12_23_src/enet]$ ./configure

: bad interpreter: No such file or directory

(23:06:55)[ivanatora@~/Archives/cube/source/cube_2003_12_23_src/enet]$ ls

aclocal.m4    depcomp    host.c      list.c      memory.o      peer.o      tutorial.txt

api.txt      design.txt  host.o      list.o      missing        protocol.c  unix.c

configure*    docs/      include/    Makefile    mkinstalldirs  protocol.o  unix.o

configure.in  Doxyfile    install-sh  Makefile.am  packet.c      pyenet/    win32.c

CVS/          enet.dsp    libenet.a  Makefile.in  packet.o      README      win32.o

demo/        enet.txt    LICENSE    memory.c    peer.c        test/

(23:06:56)[ivanatora@~/Archives/cube/source/cube_2003_12_23_src/enet]$ ./configure

: bad interpreter: No such file or directory

(23:07:50)[ivanatora@~/Archives/cube/source/cube_2003_12_23_src/enet]$ /home/ivanatora/Archives/cube/source/cube_2003_12_23_src/enet/configure

: bad interpreter: No such file or directorycube_2003_12_23_src/enet/configure: /bin/sh

The file is there, I can see it via ls, but when I try to execute it, the shell says it doesn't exist.. I can see it via mc, too, but can't execute it too.. Already toggled +x flag. Am I doing something wrong or it's nasty system's fault!?

it says.. configure*

not configure...

try ./configure*

what's the first relevant line in the file? #!/bin/sh or something?

The * just denotes it as executable. Notice that the directories have / after the names. It's probably an ls alias doing that.

As for the original question about the bad interpreter, the first line of the configure script is what's broken. Check that the #! file actually exists. Also, make sure that there are no ^M in the file.

Thanks! There was a space: "#! /bin/sh" :) Now it almost work.. there are similar mistakes all trough the configure scripts..
Thanks for the idea, again :)