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
Date: Mon, 02 Jun 2003 11:21:34 -0500 (EST)
Message-Id: <20030602.112134.56958549.wscott@bitmover.com>
To: cygwin AT cygwin DOT com, autoconf AT gnu DOT org
Subject: CYGWIN enviroment conflicts with autoconf configure scripts
From: Wayne Scott <wscott AT bitmover DOT com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I have been debugging a problem in Windows under the Cygwin
enviroment, where a autoconf configure script would fail to run
correctly if the user executing the script was not the same person
that installed cygwin.

I debugged this to the following problem:  We have been using
CYGWIN=nontsec to make the permissions work.

CYGWIN is a enviromental variable used by CYGWIN for a number of different
purposes.

	http://cygwin.com/cygwin-ug-net/setup-env.html

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.


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
cygwin 1.3.22

Thanks,

-Wayne

--
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/