Dan.Pinvidic has asked for the wisdom of the Perl Monks concerning the following question:
Our current method to run perl, is a wrapper script which determines what machine you are on, and finaly calls the correct PERL executable. The script begins with #!/usr/bin/sh. Now my personal perl script begins with: #!/usr/bin/env /bin/perl_wrapper -w this problem is a Unix problem where the -w is interpreted as a file name, and I get a -w file not found error. If I remove the -w, the nested scripts work fine. Is there another method to have the first line of my personal PERL script call a wrapper (for binary selection) and still pass perl options. Or a bteer way to select the right binary? Users may want specific perl versions. Thanks, Dan
#!/usr/bin/env perl_wrap -w #Above line fails with -w not found #!/usr/bin/env perl_wrap #Above line works fine
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: How can I control perl binaries
by frozenwithjoy (Priest) on Jun 23, 2012 at 00:38 UTC | |
|
Re: How can I control perl binaries
by 2teez (Vicar) on Jun 23, 2012 at 01:03 UTC | |
by Dan.Pinvidic (Initiate) on Jun 23, 2012 at 02:16 UTC | |
by 2teez (Vicar) on Jun 23, 2012 at 02:51 UTC | |
|
Re: How can I control perl binaries
by Anonymous Monk on Jun 23, 2012 at 07:30 UTC | |
by aaron_baugher (Curate) on Jun 23, 2012 at 16:52 UTC | |
by Dan.Pinvidic (Initiate) on Jun 25, 2012 at 17:51 UTC |