This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: (setup.ini) autoconf requires Perl?

--- "Patrick J. LoPresti" <> wrote:
> Nicholas Wourms <> 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
> 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:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]