perl module install?

DKY · 08-02-2003, 06:45 PM

my permissions on this are at 0777, and I was in the cgi-bin directory, which is where it resides. But I'll try again, maybe I missed something.

DKY · 08-02-2003, 06:48 PM

Here's what I came up with, any ideas?

[root@DKY cgi-bin]# ls
htsearch iBtest.cgi namazu.cgi qtest
[root@DKY cgi-bin]# ./iBtest.cgi
: bad interpreter: No such file or directory
[root@DKY cgi-bin]#

stickman · 08-02-2003, 07:49 PM

Quote:

Originally posted by DKY
here's what happened when I tried to run the script.
./iBtest.cgi
: bad interpreter: No such file or directory

Vi the file and look for ^M and the end of the lines. If you see them, they need to be removed.

DKY · 08-02-2003, 11:02 PM

Quote:

Originally posted by stickman
Vi the file and look for ^M and the end of the lines. If you see them, they need to be removed.

How does one do that exactly, what does Vi mean?

elam · 08-02-2003, 11:34 PM

vi is a text editor.
type vi iBtest.cgi, and it should bring up the file.

You see any ^M? You can delete them with the x key and move around the screen with the ijkl keys.

to save the file, type :w and to quit type :q or more conveniently type :wq.

If you get in any trouble, use the esc key.
Documentation here

You might wanna back up the file first though. vi can be tricky.

DKY · 08-03-2003, 08:08 AM

I couldnt find any ^M, what are those anyway. I looked for it in vi, then I even opened the file in gedit, and used the find function. Nothing I found three of these though. $^O

elam · 08-03-2003, 09:11 AM

i found this on google. Might be worth a shot.
I think thats what the ^M's are. Plain text or something. You got this script from a website right?

DKY · 08-03-2003, 09:15 AM

yeah, I got it from a website, and it works on my windows server just fine. All I have to do is change the shebang line to point to perl. I dont get it.

jharris · 08-04-2003, 06:14 AM

What's the output of ls -la /usr/bin/perl it sounds be me like its the perl binary that isn't right. The #!/usr/bin/perl line is the very first line yeah? With no white space before it yeah?

cheers

Jamie...

DKY · 08-04-2003, 08:40 AM

here's the output when I open a terminal, and do the above.

Quote:

[root@DKY root]# ls -la /usr/bin/perl
-rwxr-xr-x 2 root root 12572 Feb 18 21:51 /usr/bin/perl
[root@DKY root]#

and the first line looks like so.
#!/usr/bin/perl
there are no spaces, before, I didnt know you couldnt have any anyway. Interesting. What does the terminal I pasted above tell you?

jharris · 08-04-2003, 09:34 AM

It doesn't tell me much to be honest. I was expecting to see either a problem with your #! line or incorrect permissions on the perl binary. The only other thing I can suggest is write yourself a little script from scratch that's just say

Code:

#!/usr/bin/perl -w

print "Hello world\n";

and try running that instead and see if you get the same error.

cheers

Jamie...

stickman · 08-04-2003, 09:46 AM

The ^M characters (really CTRL-M, but displayed as ^M) come into play when transfering a file from Windows to Linux/Unix. Windows and Linux/Unix deal with the end-of-line and carriage-return differently. You are probably getting the bad interpreter error because it's looking for perl^M instead of perl. If you have them, you might want to run dos2unix on the file or use your favorite sed expression to remove them.

DKY · 08-04-2003, 10:49 AM

hello worlds works, and since I couldnt find any ^M's I thought well, if its any possible linux to windows thing, I'll go redownload the file from the "linux" site, and now everything works. Any idea as to why I didnt see any ^M. Not even after the shebang?

stickman · 08-04-2003, 11:31 AM

^M is a "hidden" or "unprintable" character. It's a carriage return. You need to make sure that whatever editor you use has a "show hidden characters" mode. ^M are introduced typically when you fetch a file from a Windows system to a Unix/Linux system.

DKY · 08-04-2003, 12:35 PM

when I used vi, I didnt see any ^M . Is there a way to have "show hidden characters" on vi? If so, how? I have a whole bunch of cgi files I want to transfer to this nix box, would it be easier to look for all the ^M's, or a dos2unix, if so.... What's the proper way to use dos2unix, just cd to the directory, and dos2unix filename.cgi??