This is the mail archive of the
mailing list for the Cygwin project.
Re: In scripts suddenly must use perl.exe rather than perl
- From: Yitzchak Scott-Thoennes <sthoenna at efn dot org>
- To: cygwin at cygwin dot com
- Date: Sun, 9 Jul 2006 13:03:09 -0700
- Subject: Re: In scripts suddenly must use perl.exe rather than perl
- References: <Xns97FB8835C5CB7zzappergmailcom@18.104.22.168>
On Sun, Jul 09, 2006 at 12:23:24PM +0000, zzapper wrote:
> I have a few (ancient) shell scripts which call perl scripts (which
> perform MySql queries), since a few days these have stopped working (may
> have been since recent coreutils update)
What does "stopped working" mean?
> c:/usr/local/bin/perl sdbk.pl $* (hard path to activestate perl)
> to get them working again I have to change perl to perl.exe
> c:/usr/local/bin/perl.exe sdbk.pl $*
> Havn't been lurking here recently but is this a known problem or brain-
> failure on my part?
What happens when you try running them directly from a shell prompt
(using the same shell as your shell script)?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html