Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Message-ID: <20020913154239.90595.qmail@web21002.mail.yahoo.com>
Date: Fri, 13 Sep 2002 08:42:39 -0700 (PDT)
From: Nicholas Wourms <nwourms@yahoo.com>
Subject: Re: (setup.ini) autoconf requires Perl?
To: "Patrick J. LoPresti" <patl@curl.com>
Cc: cygwin@cygwin.com
In-Reply-To: <s5gu1ktdhve.fsf@egghead.curl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


--- "Patrick J. LoPresti" <patl@curl.com> wrote:
> Nicholas Wourms <nwourms@yahoo.com> writes:
> 
> > Not in autoconf 2.5x...  This version is totally dependant on
> perl
> > for all generation activities.  So setup is absolutely correct in
> > requiring perl.  AFAIK, there isn't a way to unbundle the perl
> > functionality either.  So my suggestion is to get over your
> dislike
> > of Cygwin perl and install it.  Many people have Cygwin perl and
> > ActiveState co-existing happily...
> > 
> > Quote straight from the autoconf README:
> > "Producing configuration scripts using Autoconf requires GNU M4
> and
> > Perl".
> 
> (CC'ing webmasters@www.gnu.org)
> 
> OK, I stand corrected.  We will live with the multiple versions of
> Perl, despite the confusion this can cause.
>

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.  It's just a matter of pinning the
heuristics down.  If you're curious, this type of methodology is how
we allow different versions of autoconf/automake/libtool to exist on
the same machine.
[SNIP]

> P.S. How about renaming Cygwin Perl to "perl" instead of
"perl.exe"?

See above for a better solution, because it is possible there are
circumstances where Cygwin will not recognize an executable binary
without the .exe extension.

Cheers,
Nicholas

__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com

--
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/

