X-Spam-Check-By: sourceware.org Date: Sun, 9 Jul 2006 13:03:09 -0700 From: Yitzchak Scott-Thoennes To: cygwin AT cygwin DOT com Subject: Re: In scripts suddenly must use perl.exe rather than perl Message-ID: <20060709200309.GA2652@efn.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Sun, Jul 09, 2006 at 12:23:24PM +0000, zzapper wrote: > Hi, > > 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)? cygcheck output? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/