Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
To:	Wayne Scott <wscott AT bitmover DOT com>
Cc:	cygwin AT cygwin DOT com, autoconf AT gnu DOT org
Subject:	Re: CYGWIN enviroment conflicts with autoconf configure scripts
References:	<20030602 DOT 112134 DOT 56958549 DOT wscott AT bitmover DOT com>
From:	Assar Westerlund <assar AT kth DOT se>
Date:	02 Jun 2003 13:38:05 -0400
In-Reply-To:	<20030602.112134.56958549.wscott@bitmover.com>
Message-ID:	<86u1b82xdu.fsf@diem-wing.mit.edu>
Lines:	14
User-Agent:	Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version:	1.0

Wayne Scott <wscott AT bitmover DOT com> writes:
> Unfortunately it is also used as a temporary variable in the autoconf
> script and so as soon as configure resets the CYGWIN variable, it was
> unable to run 'gcc' anymore.

It's only set by the (now obsolete) AC_CYGWIN macro.

> Autoconf needs to be changes to not trash the CYGWIN variable when
> running it's tests.  And Cygwin developers need to beware of this
> problem when trying to build programs.
>
> autoconf v2.13

You need to update autoconf and migrate away from obsolete macros.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -