Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: From: "McDermott, Alastair" To: cygwin AT sourceware DOT cygnus DOT com Cc: michael-ring AT t-online DOT de Subject: RE: Problems building autoconf Date: Tue, 11 Jul 2000 12:33:55 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) 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 AT sourceware DOT cygnus DOT com