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 X-Originating-IP: [194.202.163.32] X-Originating-Email: [pratab_a AT hotmail DOT com] From: "Pratab Ali" To: cygwin AT cygwin DOT com Subject: cygwin version 1.3.21(0.77/3/2) [bash shell :: exporting mixed-case environment] Date: Wed, 02 Apr 2003 12:25:58 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 02 Apr 2003 12:25:58.0467 (UTC) FILETIME=[03E29130:01C2F913] Hello, Have been using a much older version of cygwin till now without any problems. It has come to our attention that exporting environment variables in the bash shell may be broken. scenario: $> cd myappdir $> export DevOS=WINNT $> make make is called in a dir which contains a "makefile" file. makefile uses the DevOS environment variable, which according to this version of cygwin is blank (does not exist). This is where the old cygwin had no issues. Closer inspection: $> env | less the env output shows that an environment variable has been created but the name of the variable is all upper case. $> export shows all exports but claims the mixed-case environment variable is mixed-case. We have tried using quotes to enclose variable name and value, but no success. Thanks and regards Pratab Ali _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/