Re: Dealing with incorrect shebang line entries on Windows with Apache

You could do:
ln -s /usr/bin/perl /usr/local/bin/perl

Update: I'd also point out that development boxes should be exactly the same as the production box. Otherwise you get horrible problems like you're having

Comment on Re: Dealing with incorrect shebang line entries on Windows with Apache

Replies are listed 'Best First'.
Re^2: Dealing with incorrect shebang line entries on Windows with Apache by tohann (Sexton) on May 04, 2005 at 16:02 UTC
Thank you for your reply. Yes, that would work, but I was hoping for something we would do locally and not have to change the server. I agree, the dev boxes should be the same as production, but that's not going to fly around here in a long, long time. I forgot to mention that we're developing on WinNT and the server is on a Linux machine. That's one more wrinkle. :) I'll modify the original post to state this important fact. Trent	[reply]
Re^3: Dealing with incorrect shebang line entries on Windows with Apache by ikegami (Patriarch) on May 04, 2005 at 16:11 UTC
You're using WinNT... Are you using ActiveState's Perl? It ignores the path in the #! line. Update: On second thought, the web server on your dev station might pay attention to it. Is there anyway you could tell your web server to use a specific Perl instead of looking at the #! line?	[reply]
Re^4: Dealing with incorrect shebang line entries on Windows with Apache by tohann (Sexton) on May 04, 2005 at 16:18 UTC
I am using ActiveState's Perl. I tried leaving it with the server's path to Perl and it wasn't to happy with me. As soon as I changed it the script started working. So I'm guessing the local web server (Apache) does look at it. I'm not an Apache expert by any means, but I haven't seen a config for that yet. That's definitely something worth looking into.	[reply]