Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <C23163F98473D311874C0008C7E62107036D43C3@daemsg02.software-ag.de>
From: "McDermott, Alastair" <Alastair.McDermott@softwareag.com>
To: cygwin@sourceware.cygnus.com
Cc: michael-ring@t-online.de
Subject: RE: Problems building autoconf
Date: Tue, 11 Jul 2000 12:33:55 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

Hi all,

> You can override the configure mechanism by setting and exporting an
> environment var named PERL.
> 
> PERL=/usr/local/bin/perl
> export PERL
> ./configure --prefix=/usr 
> 
> should now work.

Should work ... and doesn't :-/ The ./configure returns the same result as
previously. I am really confused now. The $PERL path is both explicitly
stated : 

bash-2.04$ echo $PERL
/usr/local/bin/perl

and implicit (should be found with this):

bash-2.04$ echo $PATH
/usr/bin:/usr/local/bin:/WINNT/system32:/WINNT: *etc*

> But something seems to be wrong with your path. What configure does
> is, that it looks for perl everywhere in the path and uses this
> information. It normally should find your perl :-(

The above would imply to me that my path is correct. Could there be a
problem with my ./configure file? Where else should I be looking?

Again, thanks for the help! 

Alastair.

--
Alastair McDermott,
Software AG R&D Ireland Ltd.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com