Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <018b01c3301d$197775b0$78d96f83@pomello> From: "Max Bowsher" To: "Hornsby, Kelly" , References: <60376EEA35F4964CA2DF6A00D72B74FD7F7F76 AT MBSP06 DOT services DOT sp DOT trw DOT com> Subject: Re: CYGWIN_NT-5.0 ZPC207050 1.3.22(0.78/3/2) bug Date: Wed, 11 Jun 2003 14:26:43 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Cam-ScannerAdmin: mail-scanner-support AT ucs DOT cam DOT ac DOT uk X-Cam-AntiVirus: Not scanned X-Cam-SpamDetails: 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? Nothing to do with Cygwin. This was a change in the upstream version of bash, in version 2.05a. This version was released as a Cygwin package in NOVEMBER 2001 !!! Your makefiles are making an invalid assumption that OSTYPE will always be defined. Fix them to not assume that. Max. -- 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/