Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
MIME-Version:	1.0
Subject:	RE: Add requirement for SYSTEMROOT to FAQ?
Date:	Thu, 7 Oct 2004 12:42:19 -0400
Message-ID:	<C1A7FA5F2793A94BA223673B8ADAF4A103746306@exchange.air2web.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"Richard Campbell" <richard DOT campbell AT air2web DOT com>
To:	<cygwin AT cygwin DOT com>
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id i97GgTi6006134

Christopher Faylor wrote:
>
>On Thu, Oct 07, 2004 at 10:20:53AM +0200, Corinna Vinschen wrote:
>>
>>What about
>>always adding SYSTEMROOT to the windows env created in build_env,
>>if it's missing?
>
>That's what I was thinking.  And then lying about its existence if
>someone queries the environment via getenv and SYSTEMROOT is "not
>supposed to be there".

Won't lying about the existence of SYSTEMROOT lead to some problems
debugging a SYSTEMROOT-related issue?

"What's the SYSTEMROOT?"

"How do I find out?"

"Add echo $SYSTEMROOT to [something]"

"It says SYSTEMROOT is empty"

etc.

-Richard Campbell.

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