Hello, An issue has recently been raised (by me) in the libtool mailing list regarding the desirability of using the label "gnu-win32" in scripts like libtool (and, I presume, configure). I seem to recall that you have an objection to linking the name "GNU" to something like "win32" because the "win" part makes it seem like the user is "winning" with a proprietary OS. Or, at any rate, this is the aprocryphal story that I heard when I started working on the Cygwin project. This is what prompted the name change from gnu-win32 to cygwin32, or at least that is what I was told. Anyway, there is now a new, unrelated project now that is billing itself as "gnu-win32" and I thought it might be a good idea to alert you to this before the name started popping up in configure and libtool scripts. We also have made the switch from cygwin32 to cygwin due to the possibility that Microsoft would sue for trademark infringement on the name "win32" (sigh). But that's probably a separate issue... -Christopher Faylor
