xlaunch small glitch

Sat Feb 28 22:25:00 GMT 2015

From: Corinna Vinschen
>> Just for your information: This change from WOW64 to WOW in the uname
> sysname output was forced on us to account for the excessive version bump in
> Windows 10.
>> Rather than bumping the kernel version to 6.4, which would have been the right
> thing to do, the marketing guys at Microsoft had the brilliant idea that the kernel
> version should finally be the same version as the marketing name of the OS. And
> since they were wailing so much, the developers caved in and made the bump.
>> So now we would have the sysname
>> CYGWIN_NT-10.0-WOW64
>> which has 20 characters, plus a trailing 0円. The sysname char array has a length
> of 20 characters, which is hard to change if we want to maintain backward
> compatibility with existing tools like uname.
>> Therefore I shortened "WOW64" to "WOW". I would have loved to change
> "CYGWIN_NT" to "CYGWIN" instead, but there are more scripts out in the wild
> explicitely testing for this, than testing for "WOW64". I didn't even know one of
> our own scripts is checking that.

How about a change to something like CYGWIN_NT-W32-10.0 and CYGWIN_NT-W64-10.0 instead?
--
cyg Simple
--
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