Re: Re: Re: Making working cross-platform scripts?

To ask the obvious: Is the script executable? (did you e.g. chmod +x script.pl?). And is the path to perl in the first line correct?, the message 'no such file or directory' is issued if the shell can't find the executable it's told to feed the script to.

regards,
tomte

Hlade's Law:

If you have a difficult task, give it to a lazy person --
they will find an easier way to do it.

Comment on Re: Re: Re: Making working cross-platform scripts?

Replies are listed 'Best First'.
Re: Re: Re: Re: Making working cross-platform scripts? by stonecolddevin (Parson) on Jul 03, 2003 at 23:49 UTC
It's chmod'd correctly (775), and I've checked the path to perl, and it's correct as well...I suppose I could still try the binary mode... Ergo!!! Vis a Vis!!! Concordidly!!! Mr. Timberlake. I apologize. I don't usually like to use my big voice. Will Ferrill as the Architect from the Matrix 2:Reloaded	[reply]
Re: Re: Re: Re: Making working cross-platform scripts? by Anonymous Monk on Jul 05, 2003 at 15:53 UTC
to follow up on that - one elephant trap in the w32<=>unix conversion is first line: `#!/usr/bin/perl` [download] If you've written that with a windows editor that line will probably be: `#!/usr/bin/perl<carriage return>` [download] so the system looks for the file `"/usr/bin/perl".chr(13)` and doesn't find it. If you're ftping the files make sure you transferred the scripts as ascii files. Run a `tr -d \\015 <filename.bad > filename.good` for good measure	[reply] [d/l] [select]