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 Date: Thu, 7 Oct 2004 10:20:53 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Add requirement for SYSTEMROOT to FAQ? Message-ID: <20041007082053.GB21753@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20041007015310.GA5938@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041007015310.GA5938@trixie.casa.cgf.cx> User-Agent: Mutt/1.4.2i On Oct 6 21:53, Christopher Faylor wrote: > Didn't we resolve that the need for SYSTEMROOT in the environment should > be in the FAQ at some point? > > Joshua, could you add something about how SYSTEMROOT is required for proper > operation with winsock? That would be good. > Or, even better yet, Corinna could we force SYSTEMROOT to be used > somehow but masked if someone removes it from the environment? Hmm, usually applications which suffer from a missing SYSTEMROOT are spawned by a parent process which has explicitely created a new environment block for the child and then calls execvp. So the new child is already missing SYSTEMROOT on process startup. What about always adding SYSTEMROOT to the windows env created in build_env, if it's missing? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/