public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Nicholas Wourms <nwourms@yahoo.com>
To: cygwin@cygwin.com
Subject: Re: (setup.ini) autoconf requires Perl?
Date: Fri, 13 Sep 2002 08:51:00 -0000	[thread overview]
Message-ID: <20020913154431.6322.qmail@web21001.mail.yahoo.com> (raw)
In-Reply-To: <Pine.GSO.4.44.0209131135560.19696-100000@slinky.cs.nyu.edu>


--- Igor Pechtchanski <pechtcha@cs.nyu.edu> wrote:
> On 13 Sep 2002, Patrick J. LoPresti 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.
> >
> > But somebody should fix the Autoconf home page
> > <http://www.gnu.org/software/autoconf/autoconf.html>, which still
> > says:
> >
> >     Some optional utilities that come with Autoconf use Perl.
> However,
> >     none of those are required in order to use the main Autoconf
> >     program. If perl is not present, the affected Autoconf
> utilities
> >     will not be installed.
> >
> >  - Pat
> >
> > P.S. How about renaming Cygwin Perl to "perl" instead of
> "perl.exe"?
> 
> If you are worried about name clashes, you're better off moving the
> ActivePerl directory to the front of your path (in /etc/profile,
> for
> example).

That won't work, because then autoconf/automake will stop working
properly, as they expect a perl which interprets POSIX naming and
path conventions.

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/

  reply	other threads:[~2002-09-13 15:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13  8:15 Patrick J. LoPresti
2002-09-13  8:33 ` Nicholas Wourms
2002-09-13  8:42   ` Patrick J. LoPresti
2002-09-13  8:44     ` Igor Pechtchanski
2002-09-13  8:51       ` Nicholas Wourms [this message]
     [not found]         ` <mit.lcs.mail.cygwin/20020913154431.6322.qmail@web21001.mail.yahoo.com>
2002-09-13 12:36           ` Patrick J. LoPresti
2002-09-13  8:52       ` Patrick J. LoPresti
2002-09-13  9:33         ` Igor Pechtchanski
2002-09-13  8:46     ` Nicholas Wourms
2002-09-13  8:54       ` Patrick J. LoPresti
2002-09-13  9:02         ` Christopher Faylor
     [not found]           ` <mit.lcs.mail.cygwin/20020913155406.GD3863@redhat.com>
2002-09-13 13:07             ` Patrick J. LoPresti
2002-09-13 10:29         ` Gerrit P. Haase
2002-09-13  8:54     ` Christopher Faylor
2002-09-13 10:54 Robinow, David
2002-09-13 13:24 Robinow, David
2002-09-13 14:02 ` Nicholas Wourms
2002-09-14  0:06 Robinow, David
2002-09-14  6:20 ` Raphael
2002-09-14  7:25   ` Nicholas Wourms

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020913154431.6322.qmail@web21001.mail.yahoo.com \
    --to=nwourms@yahoo.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).