Re: new sh doesn't translate Unix-style paths for Perl?

[Charles Wilson <cwilson at ece dot gatech dot edu>]

FYI, Geoff Hart contribed a stub executable to assist in running
ActiveState perl from cygwin.  It is provided as-is, but it may help
your situation:

http://cygutils.netpedia.net/unversioned/perl-contrib/index.html

--Chuck


John Pollock wrote:
> 
> >Does it work in bash?  Was your old "sh" ash or bash?
> 
> Our old "sh" was ash.  To answer the other points, i understand that
> ActiveState Perl may not be properly parsing the paths, but the old sh
> appeared to do some sort of translation on its behalf.  Switching to a
> different version of Perl at this point is going to be difficult for us, so
> i was hoping to be able to use the new sh without losing any of the previous
> functionality.  And i'm still not sure i understand why ./ invocations of
> Perl scripts don't work with the new sh, as they did with the old.
> 
> One of my motivations for trying to use the new sh is that we've been seeing
> a lot of "Can't send signal 20" errors and make segmentation faults since we
> upgraded from b20 to v1.1.4 (we're at the very latest version as of
> yesterday), but we hadn't upgraded sh because of some of the issues like the
> one above.  I was hoping that upgrading sh (which is invoked by make) might
> lessen some of these problems, but perhaps that wouldn't happen anyway.
> 
> I appreciate all the feedback so far!  Thanks all!
> John
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com