Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 To: Nicholas Wourms Cc: cygwin AT cygwin DOT com Subject: Re: (setup.ini) autoconf requires Perl? References: <20020913154239 DOT 90595 DOT qmail AT web21002 DOT mail DOT yahoo DOT com> From: "Patrick J. LoPresti" Date: 13 Sep 2002 11:52:04 -0400 In-Reply-To: <20020913154239.90595.qmail@web21002.mail.yahoo.com> Message-ID: Lines: 20 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Nicholas Wourms writes: > Your best bet is to move the Cygwin perl.exe to a new directory which > isn't in PATH. Then you can make a wrapper script called "perl", > which resides in bin, that parses the arguments passed to it. I > haven't used ActiveState myself, but I'm sure there are consistant > differences between the two. Nothing you could easily detect by a heuristic, I am afraid. The biggest difference is probably that ActiveState does not know about Cygwin paths (and Cygwin does not supply the Win32 module (?)). So "/foo" has meaning to each; it just means something different... Heuristics are often a poor design. The author of the Perl code knows which version she wants; she should have a way to specify it. "perl" vs. "perl.exe" is not a perfect solution, but it is at least as good as any of the others I have seen. - Pat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/