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
>
> --Andrew Black
>
> Farid Zaripov wrote:
>
>>> -----Original Message-----
>>> From: Andrew Black [mailto:ablack@roguewave.com] Sent: Monday,
>>> October 30, 2006 6:06 PM
>>> To: stdcxx-dev@incubator.apache.org
>>> Subject: Re: Windows infrastructure bug
>>>
>>> It was attached as test~bat.txt (with the original name being test.bat)
>>> I assume that a mail server (probably the apache list server)
>>> mangled the file name as a safety measure.
>>>
>>> The contents of the file are very simple though:
>>>
>>>> call generate.bat /CONFIG:msvc-8.0 /BUILDDIR:%~dp0\build
>>>
>>> /LOCALES:no
>>>
>>>> /LOCALETESTS:no
>>>>
>>>> call build\build_msvc-8.0.bat 15d
>>
>>
>> I can't reproduce the bug on my workstation.
>>
>> BTW I don't see the output from the compiler within config.log file
>> (only linker output is present).
>>
>> I discovered that cl.exe (MSVC 8.0) redirect output to the named pipe
>> instead of console
>> If VS_UNICODE_OUTPUT environment variable is set:
>> http://blogs.msdn.com/freik/archive/2006/04/05/569025.aspx
>>
>> I've updated configure.wsf script:
>> http://svn.apache.org/viewvc?view=rev&rev=469534
>>
>> Please, try this and sent to me the new config.log file if this
>> problem still present.
>>
>> Farid.
|