Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <4547E516.8010602@roguewave.com>
Date: Tue, 31 Oct 2006 17:06:46 -0700
From: Andrew Black <ablack@roguewave.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: Re: Windows infrastructure bug
References: <F92433E3D38672499C549EB615AFADA099964D@exkiv.kyiv.vdiweb.com>
 <45479F29.4020007@roguewave.com> <4547D246.2090200@roguewave.com>
In-Reply-To: <4547D246.2090200@roguewave.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Martin Sebor wrote:
> Andrew Black wrote:
>> Greetings Farid.
>>
>> I checked the provided test case again on my local installation, and 
>> discovered that it does not replicate the issue.
>>
>> After further digging, I have found that the problem seems to have 
>> been the use of the %G or %H variable in a for loop prior to invoking 
>> devenv.  This was worked around by using the SETLOCAL/ENDLOCAL 
>> directives.
>>
>> As batch scripts alter their environment unless the SETLOCAL command 
>> is used, I had been reducing my test case in an environment where 
>> these variables were undesirably set.
> 
> So is the original problem now resolved?
> 
> Martin

Kinda.

The glue script now works (and making the variables local I believe to 
be a positive change), but the observed issue of stray environment 
variables throwing the sanity test script off probably should be looked 
into at some point.

--Andrew Black