On Mon, Aug 21, 2023, at 1:17 AM, Po Lu wrote:
> Jacob Bachmeyer writes:
>
> > No: MinGW is Windows native "Win32" API while a future `windows-gnu'
> > would be the GNU system's POSIX API on an NT kernel. These are *very*
> > different configurations; `windows-gnu' would more closely resemble
Po Lu wrote:
Jacob Bachmeyer writes
This is why I am arguing that we should acknowledge that the naming
conventions have, in practice, already changed to
CPU-VENDOR-KERNEL-OS-LIBCABI, with only 3-or-4-of-5 elements present
at the moment.
$ ./config.sub a-b-c-d-e
Invalid configuration
Po Lu wrote:
Jacob Bachmeyer writes:
No: MinGW is Windows native "Win32" API while a future `windows-gnu'
would be the GNU system's POSIX API on an NT kernel. These are *very*
different configurations; `windows-gnu' would more closely resemble
Cygwin.
This is not what the
Po Lu wrote:
Jacob Bachmeyer writes:
[...]
but several existing tuples use a libc or ABI name in place of a
kernel and/or operating system.
In each of those cases, the ABI name _can_ be construed as a kernel
(since there is no kernel at all), or the libc name refers to a
Jacob Bachmeyer writes:
> No, we are not. CPU-VENDOR-KERNEL-OS-LIBCABI, with at least one of
> the latter three omitted, fits the bill. In that case, the reference
> to MinGW means that "OS" and/or "KERNEL" are omitted and MinGW is the
> ABI. The next logical extension is to allow all five to
Jacob Bachmeyer writes:
> I said "with only 3-or-4-of-5 elements present"; that using all 5
> elements is currently invalid does not change that we effectively
> /have/ 5 elements, with a restriction that only 3 or 4 of them can
> actually be present in any one tuple.
>
>
> -- Jacob
And my
John Ericson wrote:
On Mon, Aug 21, 2023, at 1:17 AM, Po Lu wrote:
Jacob Bachmeyer mailto:jcb62...@gmail.com>> writes:
> No: MinGW is Windows native "Win32" API while a future `windows-gnu'
> would be the GNU system's POSIX API on an NT kernel. These are *very*
> different configurations;
Jacob Bachmeyer writes:
> Then its present use is *wrong* and a bug that should be fixed.
The subject of this thread, indeed.
> It is a little more complex than that: the GNU system theoretically
> can run on any of multiple kernels. While Linux is most commonly
> used, GNU HURD is still in
"John Ericson" writes:
> I have offered multiple times to change it to windows-mingnu or
> something else. Let's not be hung up on this, it is just making a straw
> man of the broader project of making configs that are more
> consistent.
The point is, it should not contain `windows' at all, and
