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: Wed, 11 Jun 2003 15:21:25 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: CYGWIN_NT-5.0 ZPC207050 1.3.22(0.78/3/2) bug Message-ID: <20030611132125.GF30116@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <60376EEA35F4964CA2DF6A00D72B74FD7F7F76@MBSP06.services.sp.trw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <60376EEA35F4964CA2DF6A00D72B74FD7F7F76@MBSP06.services.sp.trw.com> User-Agent: Mutt/1.4.1i On Wed, Jun 11, 2003 at 06:04:40AM -0700, Hornsby, Kelly wrote: > I just discovered that an environment variable OSTYPE is not longer exported by default to a subprocess under this version of Cygwin. Why did this occur? Was it intentional, or inadvertent? I use this often, and although I can perform an export OSTYPE explicitly, I now have lots of broken makefiles that won't work anymore. Do you have any suggestions? Otherwise, can this guy be fixed in the next minor release? Quote from the bash 2.05 CHANGES file: Bash no longer auto-exports HOSTNAME, HOSTTYPE, MACHTYPE, or OSTYPE, even if it assigns them default values. export OSTYPE in your profile will help. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer 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/