This is the mail archive of the
mailing list for the Cygwin project.
Re: (setup.ini) autoconf requires Perl?
- From: Nicholas Wourms <nwourms at yahoo dot com>
- To: "Patrick J. LoPresti" <patl at curl dot com>
- Cc: cygwin at cygwin dot com
- Date: Fri, 13 Sep 2002 08:42:39 -0700 (PDT)
- Subject: Re: (setup.ini) autoconf requires Perl?
--- "Patrick J. LoPresti" <email@example.com> wrote:
> Nicholas Wourms <firstname.lastname@example.org> writes:
> > Not in autoconf 2.5x... This version is totally dependant on
> > 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
> > 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
> > Perl".
> (CC'ing email@example.com)
> 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.
> P.S. How about renaming Cygwin Perl to "perl" instead of
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.
Do you Yahoo!?
Yahoo! News - Today's headlines
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html