This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Environment passing bug?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 21 Feb 2012 10:50:25 +0100
- Subject: Re: Environment passing bug?
- References: <4F42D201.4000901@cwilson.fastmail.fm>
- Reply-to: cygwin at cygwin dot com
On Feb 20 18:06, Charles Wilson wrote:
> I've observed different behavior with cygwin-1.7.0 on 64bit XP, and
> 32bit XP (I'll check Vista-32 and W7-64 later tonight). Using the
> following attached win32 program:
>
> $ i686-pc-mingw32-gcc -o envprint envprint.c
>
> ====== xp-64 ========
> $ uname -a
> CYGWIN_NT-5.2-WOW64 abcdefgh 1.7.10(0.259/5/3) 2012-02-05 12:36 i686 Cygwin
>
> $ ./envprint | grep -i temp
> 'TEMP=C:\cygwin\tmp'
> ====== xp-64 ========
>
>
>
> ====== xp-32 ========
> $ uname -a
> CYGWIN_NT-5.1 ijklmnopq 1.7.10(0.259/5/3) 2012-02-05 12:36 i686 Cygwin
>
> $ ./envprint | grep -i temp
> 'TEMP=C:\cygwin\tmp'
> 'temp=C:\TEMP'
> 'tmp=C:\TEMP'
> ====== xp-32 ========
What I'm missing here is the information how the environment looks
like in terms of the TMP/TEMP variables *before* calling envprint.
Without this the testcase is rather incomplete.
For testing I did
tcsh$ setenv TEMP /tmp
tcsh$ setenv TMP /tmp
tcsh$ ./envprint | grep -i tmp
'TEMP=C:\cygwin\tmp'
'TMP=C:\cygwin\tmp'
same result on 32 bit W7 and 64 bit W2K8R2.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple