Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Add requirement for SYSTEMROOT to FAQ? Date: Thu, 7 Oct 2004 12:42:19 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Richard Campbell" To: X-IsSubscribed: yes Content-Transfer-Encoding: 8bit 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/