bug#24956: 26.0.50; On Windows, setting PATH in compilation-environment has no effect

[Noam Postavsky]

tag 24956 fixed
close 24956
quit

On Sun, Nov 27, 2016 at 3:13 PM,  <npostavs@users.sourceforge.net> wrote:
> Óscar Fuentes <ofv@wanadoo.es> writes:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>>> Oops. Looking at Fupcase, I had somehow thought that unibyte vs
>>>> multibyte would be a problem (and hence I should use Fcompare_strings
>>>> to hide the details), but actually (as I think you've mentioned
>>>> before) that's not the case for environment variables.
>>>>
>>>> Here's a new patch.
>>>
>>> Looks OK to me, thanks.
>>
>> Ping.
>>
>> I'll like to mark this as resolved. Noam?
>
> I'm not in front of my Windows box right now, I'm planning to push this 
> tomorrow.

Pushed as 753c565df6 "Upcase Path and ComSpec in process-environment".