On Wed, May 19, 2010 at 4:46 PM, Wes Hardaker <
[email protected]> wrote:
> >>>>> On Wed, 19 May 2010 12:14:52 +0200, Bart Van Assche <
> [email protected]> said:
>
> BVA> * This Perl interpreter tries to start the POSIX shell script
> run_olducd
> BVA> with the cmd.exe interpreter, which fails.
>
> Choices:
>
> 1) figure out why perl fails to properly execute a posix shell
> automatically.
> 2) insert a shell invocation prior to the script file. But that
> requires our script to understand what the sub-script is written in
> (perl, python, bash, csh, ...). This is one of those things that in
> the unix world we expect the OS to do based on the magic first few
> bytes and in windows the expectation is that the file name contains
> the suffix type. So we could:
> 3) change the suffix type of the run_ script to .sh
> 4) If you have a broken perl system that doesn't know how to invoke
> sub-scripts properly (IE, one of the above fixes isn't in place or
> doesn't work), you can always run "make test PERL=" and that should
> get back to the verbose "unparsed" output I'd think.
>
Option (4) is now invoked automatically if necessary. See also r19059.
Bart.
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
