Jacob Bachmeyer <jcb62...@gmail.com> writes: > At this time, yes. However, the GNU utilities are designed to be > fairly portable and the NT kernel was designed to support multiple > ABIs, so a hypothetical port of GNU to run under MS-Windows is within > the realm of possibility. (In fact, the underlying architecture of NT > should have all of the primitives needed to support HURD or a closely > related system.) It is more likely that this would be implemented on > ReactOS (which aims for ABI compatibility with NT 5.1, is a stable > target, and is Free) first, but a hypothetical `x86_64-pc-windows-gnu' > (or perhaps `x86_64-pc-reactos-gnu') config tuple *is* a future > possibility.
This hypothesizing is not relevant here. x86_64-pc-windows-* represents MinGW, and should be normalized correspondingly. > And what would we canonicalize `x86_64-pc-windows-gnu' to, other than > itself, currently? x86_64-pc-mingw64, which I mentioned at the outset of this thread. > It appears that config tuples may be drifting towards a 5-element > CPU-VENDOR-KERNEL-OS-LIBCABI form, with each of the last three > elements potentially optional, which makes any real tuple ambiguous, > except that the valid strings for KERNEL, OS, and LIBCABI are from > distinct sets. Configuration tuples don't ``drift'', and they certainly should not change or duplicate other triplets.
